Bug#985288: chai: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

[Yadd]

Le 15/03/2021 à 19:42, Andreas Beckmann a écrit :
> On 15/03/2021 14.00, Yadd wrote:
>> Le 15/03/2021 à 13:49, Yadd a écrit :
>>> Le 15/03/2021 à 13:30, Andreas Beckmann a écrit :
 Package: chai
 Version: 4.2.0+ds+~4.2.14-3
> 
>>> there is already a maintscript for this:
>>>
>>>    $ cat debian/chai.maintscript
>>>    dir_to_symlink /usr/share/doc/chai libjs-chai 4.2.0+ds-2~
>>>
>>> What is wrong here ?
>>
>> Found: s/dir_to_symlink/symlink_to_dir/ :-(
> 
> Don't forget to bump the version in the maintscript to
> 4.2.0+ds+~4.2.14-4~ (if you are uploading 4.2.0+ds+~4.2.14-4)
> s.t. this gets cleaned up even if a buggy package was already installed.

Hi,

of course I bumped version

Cheers,
Xavier

Bug#985329: solved upgrading to experimental

[PICCORO McKAY Lenz]

i have older packages yet in my install, i dont know how happened..
but do not close this bug until i found why happened

after check and forces proper upgraded in xperimental.. is working

Lenz McKAY Gerardo (PICCORO)
http://qgqlochekone.blogspot.com

Bug#985329: courier-mta not startable/configurable due mkesmtpdcert

[PICCORO McKAY Lenz]

Package: courier-mta
Version: 1.0.16-3
Severity: grave
Justification: renders package unusable

i guess real reason of bug #984696 and #984694 is that the
mkesmtpdcert tool has an error: check this sequence:

it seems that the script put the pem file in the /usr/lib/courier
event in /etc/courier, or maybe permission problems

serveruno:/etc/courier# mkesmtpdcert
/etc/courier/esmtpd.pem already exists.
serveruno:/etc/courier# rm /etc/courier/emstpd.pem
rm: no se puede borrar '/etc/courier/emstpd.pem': No existe el fichero
o el directorio
serveruno:/etc/courier#

Markus.. the problem is not the smtpaccess.dat or imapaccess.dat so
please check this again .. just run the script .. if you could
reproduce it.. mark #984696 and #984694 as real solved  i m still
coding at the scripts but i just testing first upgrade xperience.. (i
never do upgrade .. just one install and 9 years of peace since
squeeze)


Lenz McKAY Gerardo (PICCORO)
http://qgqlochekone.blogspot.com

Bug#985245: src:ppmd: reintroduced with lower version number, different project?

[Sandro Tosi]

> > alright, i've uploaded src:python-ppmd right now, which is just a
> > rename of the src:ppmd package.
> >
> > Sean, do you need me to file a RM for src:ppmd or will dak
> > automagically take care of it?
>
> I don't believe it will happen automatically.

ok, i've filed #985326 for src:ppmd removal - let me know if there's
any other step i need to do

regards,
-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi

Bug#985245: src:ppmd: reintroduced with lower version number, different project?

[Sean Whitton]

Hello,

On Mon 15 Mar 2021 at 08:47PM -04, Sandro Tosi wrote:

> alright, i've uploaded src:python-ppmd right now, which is just a
> rename of the src:ppmd package.
>
> Sean, do you need me to file a RM for src:ppmd or will dak
> automagically take care of it?

I don't believe it will happen automatically.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#985245: src:ppmd: reintroduced with lower version number, different project?

[Sean Whitton]

Hello,

On Sun 14 Mar 2021 at 09:39PM -04, Sandro Tosi wrote:

>> Per Policy 3.2.2 this is actually RC, and there is no length of time
>> after which it's Policy-compliant to reuse package name--version pairs:
>> "the version numbers which a binary package must not reuse includes the
>> version numbers of any versions of the binary package ever accepted into
>> the archive".
>>
>> Please take a look at that section of Policy.  Unfortunately, I think
>> you're going to have to introduce an epoch.
>
> meh, at this point i'd rather do a one-time only operation: remove
> src:ppdm and reintroduce it as src:python-ppdm.
>
> is there anything that i need to other than file a RM bug for src:ppdm
> and then upload a new src:python-ppdm for making this transition
> complete?

I haven't worked through all the details, but I don't believe there is
anything else.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Processed: Re: Bug#985052: python-sympy-doc: postinst uses /usr/share/doc content (Policy 12.3): /usr/share/doc/python-sympy-doc/sympy-live.sh

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #985052 [python-sympy-doc] python-sympy-doc: postinst uses /usr/share/doc 
content (Policy 12.3): /usr/share/doc/python-sympy-doc/sympy-live.sh
Added tag(s) patch.

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

Bug#985052: python-sympy-doc: postinst uses /usr/share/doc content (Policy 12.3): /usr/share/doc/python-sympy-doc/sympy-live.sh

[Stuart Prescott]

Control: tags -1 + patch

https://salsa.debian.org/science-team/sympy/-/merge_requests/2


-- 
Stuart Prescotthttp://www.nanonanonano.net/   
stu...@nanonanonano.net
Debian Developer   http://www.debian.org/ stu...@debian.org
GPG fingerprint90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 
F2F7

Bug#985245: src:ppmd: reintroduced with lower version number, different project?

[Sandro Tosi]

alright, i've uploaded src:python-ppmd right now, which is just a
rename of the src:ppmd package.

Sean, do you need me to file a RM for src:ppmd or will dak
automagically take care of it?

Regards,
Sandro

On Sun, Mar 14, 2021 at 9:51 PM Paul Wise  wrote:
>
> On Sun, 2021-03-14 at 21:44 -0400, Sandro Tosi wrote:
>
> > but other paragraphs do (i think) :)
>
> Ah, I see!
>
> > there's no guarantee (althought i find it highly unlikely) that
> > src:ppmd will not reach the same version of the old ppmd that used to
> > be present in the archive a decade ago.
>
> The requirement is easy to workaround though, by appending extra chars
> to the affected versions, but that means remembering the requirement.
> Of course just renaming the source package is a much simpler fix.
>
> I think just uploading src:python-ppmd will fix this since src:ppmd
> will get autoremoved by the dak decrufting since src:python-ppmd will
> take over the binary packages of src:ppmd with newer versions.
>
> --
> bye,
> pabs
>
> https://wiki.debian.org/PaulWise



-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi

Bug#983684: mupdf: CVE-2021-3407

[Bastian Germann]

On Sun, 28 Feb 2021 13:33:23 +0100 Salvatore Bonaccorso 
 wrote:

CVE-2021-3407[0]:
| A flaw was found in mupdf 1.18.0. Double free of object during
| linearization may lead to memory corruption and other potential
| consequences.


See #983104 for a NMU RFS with the fix for buster.

Processed: 983684

[Debian Bug Tracking System]

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

> found 983684 1.14.0+ds1-4+deb10u2
Bug #983684 {Done: Salvatore Bonaccorso } [src:mupdf] mupdf: 
CVE-2021-3407
Marked as found in versions mupdf/1.14.0+ds1-4+deb10u2.
> tags 983684 buster
Bug #983684 {Done: Salvatore Bonaccorso } [src:mupdf] mupdf: 
CVE-2021-3407
Added tag(s) buster.
>
End of message, stopping processing here.

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

Bug#985319: golang-gopkg-alecthomas-kingpin.v2-dev: missing (unversioned) Breaks+Replaces: golang-gopkg-alecthomas-kingpin.v3-dev

[Andreas Beckmann]

Package: golang-gopkg-alecthomas-kingpin.v2-dev
Version: 2.2.6-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + golang-github-gohugoio-hugo-dev

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'buster'.
It installed fine in 'buster', then the upgrade to 'bullseye' 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 
.../081-golang-gopkg-alecthomas-kingpin.v2-dev_2.2.6-2_all.deb ...
  Unpacking golang-gopkg-alecthomas-kingpin.v2-dev (2.2.6-2) over (2.2.6-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-MCcm5P/081-golang-gopkg-alecthomas-kingpin.v2-dev_2.2.6-2_all.deb
 (--unpack):
   trying to overwrite '/usr/share/gocode/src/github.com/alecthomas/kingpin', 
which is also in package golang-gopkg-alecthomas-kingpin.v3-dev 
3.0~git20180227.b8d601d-1

golang-gopkg-alecthomas-kingpin.v3-dev is gone from the archive,
therefore the B+R can be unversioned.


cheers,

Andreas


golang-github-gohugoio-hugo-dev_None.log.gz
Description: application/gzip

Processed: golang-gopkg-alecthomas-kingpin.v2-dev: missing (unversioned) Breaks+Replaces: golang-gopkg-alecthomas-kingpin.v3-dev

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + golang-github-gohugoio-hugo-dev
Bug #985319 [golang-gopkg-alecthomas-kingpin.v2-dev] 
golang-gopkg-alecthomas-kingpin.v2-dev: missing (unversioned) Breaks+Replaces: 
golang-gopkg-alecthomas-kingpin.v3-dev
Added indication that 985319 affects golang-github-gohugoio-hugo-dev

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

Bug#985284: [Debian-med-packaging] Bug#985284: hyphy-common: unhandled symlink to directory conversion: /usr/lib/hyphy -> ../share/hyphy

[Étienne Mollier]

Andreas Beckmann, on 2021-03-15 13:21:28 +0100:
> >From the attached log (scroll to the bottom...):
> 
> 0m33.7s ERROR: installs objects over existing directory symlinks:
>   /usr/lib/hyphy/bin (hyphy-common) != /usr/share/hyphy/bin (?)
> /usr/lib/hyphy -> ../share/hyphy
>   /usr/lib/hyphy/bin/simd-dispatch (hyphy-common) != 
> /usr/share/hyphy/bin/simd-dispatch (?)
> /usr/lib/hyphy -> ../share/hyphy

Hi Andreas,

Ouch, looking up that issue, it turns out that would be me
having deleted the d/hyphy-common.links file with commit
5cc7d1a7d2bf6008cd70e422f09edfce856d25e7 while drowning it in an
unrelated change.  I'm sorry for the confusion it caused.  :(

Reintroducing the link triggers various lintian errors and
warnings, so my initial change from version 2.5.18+dfsg-1 might
have been justified actually.  I acknowledge the bug and am
seeing how to untangle this.

Many Thanks for having spotted that problem!
-- 
Étienne Mollier 
Fingerprint:  8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
Sent from /dev/pts/1, please excuse my verbosity.


signature.asc
Description: PGP signature

Bug#985317: gimp: GIMP fails to start; "GEGL operation missing" .

[Carlos Aguilar]

Package: gimp
Version: 2.10.22-2
Severity: grave
Tags: upstream
Justification: renders package unusable
X-Debbugs-Cc: hacerespa...@gmail.com

Dear Maintainer,

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

   * What led up to the situation?
GIMP required a missing dependency, in this case the graphviz package, which
rendered GIMP unusable as it could not be started without satisfying the
missing dependency.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
Manually installing the graphviz package solved the issue. See
https://gitlab.gnome.org/GNOME/gegl/-/commit/1f50456de59c686941a861d299a63bfcd4126ee5
and https://bugs.archlinux.org/task/69816 .

   * What was the outcome of this action?
GIMP now starts as expected.

   * What outcome did you expect instead?

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


-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-4-amd64 (SMP w/4 CPU threads)
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 gimp depends on:
ii  gimp-data2.10.22-2
ii  libaa1   1.4p5-48
ii  libbabl-0.1-01:0.1.86-1
ii  libbz2-1.0   1.0.8-4
ii  libc62.31-9
ii  libcairo21.16.0-5
ii  libfontconfig1   2.13.1-4.2
ii  libfreetype6 2.10.4+dfsg-1
ii  libgcc-s110.2.1-6
ii  libgdk-pixbuf-2.0-0  2.42.2+dfsg-1
ii  libgdk-pixbuf2.0-0   2.40.2-2
ii  libgegl-0.4-01:0.4.28-2
ii  libgexiv2-2  0.12.1-1
ii  libgimp2.0   2.10.22-2
ii  libglib2.0-0 2.66.7-2
ii  libgs9   9.53.3~dfsg-7
ii  libgtk2.0-0  2.24.33-1
ii  libgudev-1.0-0   234-1
ii  libharfbuzz0b2.7.4-1
ii  libheif1 1.11.0-1
ii  libilmbase25 2.5.4-1
ii  libjpeg62-turbo  1:2.0.6-4
ii  libjson-glib-1.0-0   1.6.2-1
ii  liblcms2-2   2.12~rc1-2
ii  liblzma5 5.2.5-2
ii  libmng1  1.0.10+dfsg-3.1+b5
ii  libmypaint-1.5-1 1.6.0-2
ii  libopenexr25 2.5.4-1
ii  libopenjp2-7 2.4.0-3
ii  libpango-1.0-0   1.46.2-3
ii  libpangocairo-1.0-0  1.46.2-3
ii  libpangoft2-1.0-01.46.2-3
ii  libpng16-16  1.6.37-3
ii  libpoppler-glib8 20.09.0-3.1
ii  librsvg2-2   2.50.3+dfsg-1
ii  libstdc++6   10.2.1-6
ii  libtiff5 4.2.0-1
ii  libwebp6 0.6.1-2+b1
ii  libwebpdemux20.6.1-2+b1
ii  libwebpmux3  0.6.1-2+b1
ii  libwmf0.2-7  0.2.8.4-17
ii  libx11-6 2:1.7.0-2
ii  libxcursor1  1:1.2.0-2
ii  libxext6 2:1.3.3-1.1
ii  libxfixes3   1:5.0.3-2
ii  libxmu6  2:1.1.2-2+b3
ii  libxpm4  1:3.5.12-1
ii  xdg-utils1.1.3-4
ii  zlib1g   1:1.2.11.dfsg-2

Versions of packages gimp recommends:
ii  ghostscript  9.53.3~dfsg-7

Versions of packages gimp suggests:
pn  gimp-data-extras  
ii  gimp-help-sv [gimp-help]  2.10.0-1
ii  gvfs-backends 1.46.2-1
ii  libasound21.2.4-1.1

Bug#985293: marked as done (neutron-common: missing Breaks: python3-neutron-fwaas)

[Debian Bug Tracking System]

Your message dated Mon, 15 Mar 2021 21:03:28 +
with message-id 
and subject line Bug#985293: fixed in neutron 2:17.1.0-2
has caused the Debian Bug report #985293,
regarding neutron-common: missing Breaks: python3-neutron-fwaas
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.)


-- 
985293: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985293
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: neutron-common
Version: 2:17.1.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + python3-neutron-fwaas

Hi,

during a test with piuparts I noticed python3-neutron-fwaas fails to
remove after the upgrade from buster to bullseye.

python3-neutron-fwaas does not exist in bullseye any longer, but does
not get removed during the upgrade. Removing the package after the
upgrade fails because it calls neutron-plugin-manage in a now
unsupported way. At least that's what I conclude from the log.

Adding a (unversioned) Breaks against the package should get it
removed before the incompatible neutron-plugin-manage script gets
unpacked.

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

  Removing python3-neutron-fwaas (1:13.0.1-7) ...
  2021-03-13 21:36:47,852 - stevedore.extension - ERROR - Could not load 
'firewall': cannot import name 'rpc' from 'neutron.common' 
(/usr/lib/python3/dist-packages/neutron/common/__init__.py)
  2021-03-13 21:36:47,869 - stevedore.extension - ERROR - Could not load 
'firewall_v2': cannot import name '_model_query' from 'neutron.db' 
(/usr/lib/python3/dist-packages/neutron/db/__init__.py)
  2021-03-13 21:36:47,870 - stevedore.extension - ERROR - Could not load 
'neutron.services.firewall.fwaas_plugin.FirewallPlugin': cannot import name 
'rpc' from 'neutron.common' 
(/usr/lib/python3/dist-packages/neutron/common/__init__.py)
  2021-03-13 21:36:47,883 - stevedore.extension - ERROR - Could not load 
'fwaas': cannot import name 'rpc' from 'neutron.common' 
(/usr/lib/python3/dist-packages/neutron/common/__init__.py)
  2021-03-13 21:36:47,886 - stevedore.extension - ERROR - Could not load 
'fwaas_v2': cannot import name 'rpc' from 'neutron.common' 
(/usr/lib/python3/dist-packages/neutron/common/__init__.py)
  2021-03-13 21:36:47,915 - neutron-plugin-manage - ERROR - Could not load 
'neutron.fwaas': cannot import name 'rpc' from 'neutron.common' 
(/usr/lib/python3/dist-packages/neutron/common/__init__.py)
  usage: neutron-plugin-manage disable
 [-h]
 [--service-plugin 
{auto_allocate,conntrack_helper,dummy,flavors,log,loki,metering,network_ip_availability,network_segment_range,ovn-router,placement,port_forwarding,qos,revisions,router,segments,tag,timestamp,trunk}]
 [--l3-extension 
{conntrack_helper,fip_qos,gateway_ip_qos,port_forwarding,snat_log,fwaas_v2_log}]
 {enable,disable}
 ...
  neutron-plugin-manage disable: error: argument --service-plugin: invalid 
choice: 'firewall_v2' (choose from 'auto_allocate', 'conntrack_helper', 
'dummy', 'flavors', 'log', 'loki', 'metering', 'network_ip_availability', 
'network_segment_range', 'ovn-router', 'placement', 'port_forwarding', 'qos', 
'revisions', 'router', 'segments', 'tag', 'timestamp', 'trunk')
  dpkg: error processing package python3-neutron-fwaas (--remove):
   installed python3-neutron-fwaas package pre-removal script subprocess 
returned error exit status 2
  dpkg: too many errors, stopping
  Errors were encountered while processing:
   python3-neutron-fwaas


cheers,

Andreas


python3-neutron-fwaas_None.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: neutron
Source-Version: 2:17.1.0-2
Done: Thomas Goirand 

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated neutron 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: Mon, 15 Mar 2021 21:18:42 +0100
Source: neutron
Architecture: source
Version: 2:17.1.0-2
Distribution: unstable
Urgency: medium
Maint

Bug#985311: libxcrypt migration blocker: inappropriate Build-Dependency: libltdl-dev during freeze

[Marco d'Itri]

On Mar 15, Helmut Grohne  wrote:

> As a workaround, I propose vendoring ltdl.m4. It is not uncommon to
Will do.

> As a long term solution, I propose demoting the libc6-dev ->
> libxcrypt-dev dependency to Recommends. Doing so shrinks the expectation
> of what build-essential provides.
It should just be removed (either other packages do depend on it or they 
do not), but I am not sure exactly of how much work this would require.

-- 
ciao,
Marco


signature.asc
Description: PGP signature

Processed: Bug#985293 marked as pending in neutron

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #985293 [neutron-common] neutron-common: missing Breaks: 
python3-neutron-fwaas
Added tag(s) pending.

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

Processed: Bug#985293 marked as pending in neutron

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #985293 [neutron-common] neutron-common: missing Breaks: 
python3-neutron-fwaas
Ignoring request to alter tags of bug #985293 to the same tags previously set

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

Bug#985293: marked as pending in neutron

[Thomas Goirand]

Control: tag -1 pending

Hello,

Bug #985293 in neutron 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/neutron/-/commit/1a01b44bd1c3fe9b5385650607fcee948b85a1dd


Add Breaks: python3-neutron-fwaas (Closes: #985293).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/985293

Bug#985293: marked as pending in neutron

[Thomas Goirand]

Control: tag -1 pending

Hello,

Bug #985293 in neutron 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/neutron/-/commit/1a01b44bd1c3fe9b5385650607fcee948b85a1dd


Add Breaks: python3-neutron-fwaas (Closes: #985293).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/985293

Bug#982833: man2html,man2html-base,manpages-it: manpage conflicts: man2html.1, hman.1

[Andreas Beckmann]

Followup-For: Bug #982833
Control: found -1 4.9.3-3

The hman(1) manpage is back:

  Preparing to unpack .../manpages-it_4.9.3-3_all.deb ...
  Unpacking manpages-it (4.9.3-3) ...
  dpkg: error processing archive 
/var/cache/apt/archives/manpages-it_4.9.3-3_all.deb (--unpack):
   trying to overwrite '/usr/share/man/it/man1/hman.1.gz', which is also in 
package man2html 1.6g-14
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/manpages-it_4.9.3-3_all.deb

Andreas

Processed: Re: man2html,man2html-base,manpages-it: manpage conflicts: man2html.1, hman.1

[Debian Bug Tracking System]

Processing control commands:

> found -1 4.9.3-3
Bug #982833 {Done: Helge Kreutzmann } [manpages-l10n] 
man2html,man2html-base,manpages-it: manpage conflicts: man2html.1, hman.1
There is no source info for the package 'manpages-l10n' at version '4.9.3-3' 
with architecture ''
Unable to make a source version for version '4.9.3-3'
Marked as found in versions 4.9.3-3 and reopened.

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

Bug#985311: libxcrypt migration blocker: inappropriate Build-Dependency: libltdl-dev during freeze

[Helmut Grohne]

Source: libxcrypt
Version: 1:4.4.18-1
Severity: serious

libxcrypt introduced a new dependency cycle:

src:libxcrypt Build-Depends on libltdl-dev (new)
libltdl-dev is built from src:libtool
src:libtool implicitly Build-Depends on libc6-dev
libc6-dev depends on libxcrypt-dev
libxcrypt-dev is built from src:libxcrypt

The change in Build-Depends is inappropriate at this point of the
freeze. Please revert and discuss how the change can be performed in a
way that does not break architecture bootstrap.

I think that libxcrypt really only needs /usr/share/aclocal/ltdl.m4.
This file happens to be part of libtool, but it is otherwise
architecture-independent and could be moved to an Arch:all package in
principle. Doing so would unbreak cross bootstrap, but I don't
understand the effects on a native bootstrap.

As a workaround, I propose vendoring ltdl.m4. It is not uncommon to
vendor m4 files for autoconf. While this usually makes updating them
hard, this seems to be an exceptional case where such vendoring could be
justifiable.

As a long term solution, I propose demoting the libc6-dev ->
libxcrypt-dev dependency to Recommends. Doing so shrinks the expectation
of what build-essential provides.

In any case, now is the wrong time to add this dependency. I'm filing it
at rc severity to prevent testing migration during the bullseye freeze.
Once bullseye is released, I no longer see a reason for it being rc even
if it remains unsolved. That should give enough time to evaluate options
and keep bullseye bootstrappable.

Helmut

Bug#985309: CVE-2021-21235

[Moritz Muehlenhoff]

Source: rust-kamadak-exif
Severity: grave
Tags: security
X-Debbugs-Cc: Debian Security Team 

https://github.com/kamadak/exif-rs/security/advisories/GHSA-px9g-8hgv-jvg2

Cheers,
Moritz

Processed: severity of 985220 is grave

[Debian Bug Tracking System]

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

> severity 985220 grave
Bug #985220 [src:velocity] velocity: CVE-2020-13936
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

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

Bug#985295: marked as done (qbs-examples: unhandled symlink to directory conversion: /usr/share/qbs/examples/cocoa-application/CocoaApplication/en_US.lproj -> en.lproj)

[Debian Bug Tracking System]

Your message dated Mon, 15 Mar 2021 18:50:47 +
with message-id 
and subject line Bug#985295: fixed in qbs 1.18.0-5
has caused the Debian Bug report #985295,
regarding qbs-examples: unhandled symlink to directory conversion: 
/usr/share/qbs/examples/cocoa-application/CocoaApplication/en_US.lproj -> 
en.lproj
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.)


-- 
985295: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985295
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: qbs-examples
Version: 1.18.0-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.

This was observed on the following upgrade paths:

  buster -> bullseye

For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#copyright-information

For other overwritten locations anything interesting may happen.

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#details-of-unpack-phase-of-installation-or-upgrade

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


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

  Preparing to unpack .../qbs-examples_1.18.0-4_all.deb ...
  Unpacking qbs-examples (1.18.0-4) over (1.12.2+dfsg-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/qbs-examples_1.18.0-4_all.deb (--unpack):
   unable to install new version of 
'/usr/share/qbs/examples/cocoa-application/CocoaApplication/en_US.lproj/Credits.rtf':
 No such file or directory
  Errors were encountered while processing:
   /var/cache/apt/archives/qbs-examples_1.18.0-4_all.deb


In buster /usr/share/qbs/examples/cocoa-application/CocoaApplication/en_US.lproj
was a symlink to en.lproj.

cheers,

Andreas


qbs-examples_1.18.0-4.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: qbs
Source-Version: 1.18.0-5
Done: Dmitry Shachnev 

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

Debian distribution maintenance software
pp.
Dmitry Shachnev  (supplier of updated qbs 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, 15 Mar 2021 21:02:24 +0300
Source: qbs
Architecture: source
Version: 1.18.0-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers 
Changed-By: Dmitry Shachnev 
Closes: 985295
Changes:
 qbs (1.18.0-5) unstable; urgency=medium
 .
   * Handle symlink to directory change in qbs-examples (closes: #985295).
Checksums-Sha1:
 b4875d15a49887e90648aa47c705eeca3460145b 2475 qbs_1.18.0-5.dsc
 c34b0918df23cd2fa67782f4a6739156d615e58e 32176 qbs_1.18.0-5.debian.tar.xz
 6b35999a304e38d3c362e0a35fe4717c274f55ae 11735 qbs_1.18.0-5_source.buildinfo
Checksums-Sha256:
 a702391b6026d884f6bb2c56c7e68212665ae459e93603d6319fa5c37c6c65e2 2475 
qbs_1.18.0-5.dsc
 f2dad1cfae274bdc2c661ae0782cef8d265bc2d1679e256519e484e42eb104a0 32176 
qbs_1.18.0-5.debian.tar.xz
 c83c6377fddd260169723e63222465932fcd92cc854da3f0ece57d2700fe0898 11735 
qbs_1.18.0-5_source.buildinfo
Files:
 886e2a200f5d3752a0ddd0eca520c20d 2475 devel op

Processed: retitle 985297 to libreoffice-common: do not use dir_to_symlink for /usr/lib/libreoffice/share/registry

[Debian Bug Tracking System]

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

> retitle 985297 libreoffice-common: do not use dir_to_symlink for 
> /usr/lib/libreoffice/share/registry
Bug #985297 [libreoffice-common] libreoffice-common: needs Conflicts against 
all packages shipping files in /usr/lib/libreoffice/share/registry
Changed Bug title to 'libreoffice-common: do not use dir_to_symlink for 
/usr/lib/libreoffice/share/registry' from 'libreoffice-common: needs Conflicts 
against all packages shipping files in /usr/lib/libreoffice/share/registry'.
> thanks
Stopping processing here.

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

Processed (with 1 error): user debian...@lists.debian.org, unarchiving 918163, usertagging 918163, affects 981484 ...

[Debian Bug Tracking System]

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

> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
> unarchive 918163
> usertags 918163 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 981484 + xul-ext-exteditor
Bug #981484 [webext-exteditor] webext-exteditor: not compatible with current 
thunderbird
Added indication that 981484 affects xul-ext-exteditor
> found 983853 3:18.6.2-1
Bug #983853 {Done: Thomas Goirand } [openstack-dashboard] 
openstack-dashboard: fails to upgrade from 'buster': Couldn't find anything to 
import: /horizon/lib/font_awesome/scss/font-awesome.scss
Marked as found in versions horizon/3:18.6.2-1.
> thanks
Stopping processing here.

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

Bug#985288: chai: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

[Andreas Beckmann]

On 15/03/2021 14.00, Yadd wrote:

Le 15/03/2021 à 13:49, Yadd a écrit :

Le 15/03/2021 à 13:30, Andreas Beckmann a écrit :

Package: chai
Version: 4.2.0+ds+~4.2.14-3



there is already a maintscript for this:

   $ cat debian/chai.maintscript
   dir_to_symlink /usr/share/doc/chai libjs-chai 4.2.0+ds-2~

What is wrong here ?


Found: s/dir_to_symlink/symlink_to_dir/ :-(


Don't forget to bump the version in the maintscript to 
4.2.0+ds+~4.2.14-4~ (if you are uploading 4.2.0+ds+~4.2.14-4)

s.t. this gets cleaned up even if a buggy package was already installed.

Andreas

Bug#956083: marked as done (autopostgresqlbackup: Fails to detect when DB dumps fail, and saves useless backups)

[Debian Bug Tracking System]

Your message dated Mon, 15 Mar 2021 18:03:23 +
with message-id 
and subject line Bug#956083: fixed in autopostgresqlbackup 1.1-1.1
has caused the Debian Bug report #956083,
regarding autopostgresqlbackup: Fails to detect when DB dumps fail, and saves 
useless backups
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.)


-- 
956083: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956083
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: autopostgresqlbackup
Version: 1.1-1
Severity: critical
Tags: upstream
Justification: causes serious data loss

Due to a human error, today I had to resort to backups to recover data from a
PostgreSQL database. In the worst possible moment, I realised that ALL of the
backups we had of this database are useless.

Turns out that when dumping the database to a huge text file, the system was
running out of disk space, and so the file is truncated.

Instead of detecting the problem, aborting the backup, and sending an email to
the administrator, autopostgresqlbackup assumes the dump finished well,
proceeded to compress the truncated dump, and continued as if nothing had
happened. This had been going on for months without me realising, and so I have
no useful backup.

I am setting the severity as critical, because this bug has made me lose real
world data today.

The sad part is that the bug is pretty trivial to fix: all commands should be
checked for non-zero return codes, probably by setting the '-e' flag at the
beginning of the script.

I can't believe this has gone this long without anybody noticing, and how many
people might be trusting this tool for their backups. I'd say this deserves to
be fixed in stable too.

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

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.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages autopostgresqlbackup depends on:
ii  bsd-mailx [mailx] 8.1.2-0.20180807cvs-1
ii  postgresql-client-common  200+deb10u3

Versions of packages autopostgresqlbackup recommends:
pn  heirloom-mailx | biabam | mutt  
ii  openssl 1.1.1d-0+deb10u2

Versions of packages autopostgresqlbackup suggests:
ii  bzip2 1.0.6-9.2~deb10u1
ii  xz-utils  5.2.4-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: autopostgresqlbackup
Source-Version: 1.1-1.1
Done: Gunnar Wolf 

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

Debian distribution maintenance software
pp.
Gunnar Wolf  (supplier of updated autopostgresqlbackup 
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: Wed, 10 Mar 2021 10:47:06 -0600
Source: autopostgresqlbackup
Architecture: source
Version: 1.1-1.1
Distribution: unstable
Urgency: medium
Maintainer: Emmanuel Bouthenot 
Changed-By: Gunnar Wolf 
Closes: 956083
Changes:
 autopostgresqlbackup (1.1-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Detect when a DB dump fails and abort operation (Closes: #956083)
Checksums-Sha1:
 96b50e84258b259bf3e7764e4ad1745bbfe08aec 1354 autopostgresqlbackup_1.1-1.1.dsc
 c6743f3843d43b119d54be5d2d8aecb04e719633 5000 
autopostgresqlbackup_1.1-1.1.debian.tar.xz
 1a0920010127e05584bf73e65435111f82875523 6588 
autopostgresqlbackup_1.1-1.1_source.buildinfo
Checksums-Sha256:
 6bd5d2cc57c9c09c137b8e08ea1336738875076b44e2d2e3b146789fcd8b3a9b 1354 
autopostgresqlbackup_1.1-1.1.dsc
 e29e17c56ca4419a0723e80058527d7c9ed14ac1c6bd4c6f8edf240526dd0e49 5000 
autopostgresqlbackup_1.1-1.1.debian.tar.xz
 8cb1589f9ca96b3ff1c80ab2257c3903608da391574d41b1cc7558a73ed9d9e1 6588 
autopostgresqlbackup_1.1-1.1_source.buildinfo
Files:
 ccdd0c5dbcc2062e6f4b54c373870228 1354 admin optional 
autopostgresqlbackup_1.1-1.1.dsc
 b1ebfc56c96b67422f1370d5e6ae0b5e 5000 admin optional 
a

Bug#962596: Divergence in Symantec CA blacklist reverting between sid and *stable?

[Julien Cristau]

On Mon, Mar 15, 2021 at 05:44:44PM +, Thorsten Glaser wrote:
> Hi Julien,
> 
> >Yes, they're different.  I'm not sure what you're asking.
> 
> the reason for the difference; sorry if I was unclear.
> 
They're different versions of the mozilla root store, so they include
different sets of CA certificates.

Cheers,
Julien

Bug#985295: marked as pending in qbs

[Dmitry Shachnev]

Control: tag -1 pending

Hello,

Bug #985295 in qbs 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/qt-kde-team/qt/qbs/-/commit/b105366022c84471ff7ada72e2f5720fb9321624


Handle symlink to directory change in qbs-examples.

en_US.lproj was changed from symlink to directory in this commit [1]
which is included in v1.18.0.

[1]: https://code.qt.io/cgit/qbs/qbs.git/commit/?id=6383cac927536922

Closes: #985295.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/985295

Processed: Bug#985295 marked as pending in qbs

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #985295 [qbs-examples] qbs-examples: unhandled symlink to directory 
conversion: 
/usr/share/qbs/examples/cocoa-application/CocoaApplication/en_US.lproj -> 
en.lproj
Added tag(s) pending.

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

Bug#985269: marked as done (libint1: ships broken library symlinks: /usr/lib/lib*-stable.so.1 -> lib*.so.1)

[Debian Bug Tracking System]

Your message dated Mon, 15 Mar 2021 17:48:50 +
with message-id 
and subject line Bug#985269: fixed in libint 1.2.1-6
has caused the Debian Bug report #985269,
regarding libint1: ships broken library symlinks: /usr/lib/lib*-stable.so.1 -> 
lib*.so.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.)


-- 
985269: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985269
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libint1
Version: 1.2.1-5
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

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

  libint1: MISSING OBJECT /usr/lib/libderiv-stable.so.1
  libint1: MISSING OBJECT /usr/lib/libint-stable.so.1
  libint1: MISSING OBJECT /usr/lib/libr12-stable.so.1

The dangling symlinks get "cleaned up" by ldconfig.

The package ships the following libraries and symlinks:

-rw-r--r-- root/root  20421064 2021-03-04 15:25 
./usr/lib/x86_64-linux-gnu/libderiv.so.1.0.0
-rw-r--r-- root/root   9215552 2021-03-04 15:25 
./usr/lib/x86_64-linux-gnu/libint.so.1.0.0
-rw-r--r-- root/root   9816208 2021-03-04 15:25 
./usr/lib/x86_64-linux-gnu/libr12.so.1.0.0
lrwxrwxrwx root/root 0 2021-03-04 15:25 ./usr/lib/libderiv-stable.so.1 
-> libderiv.so.1
lrwxrwxrwx root/root 0 2021-03-04 15:25 ./usr/lib/libint-stable.so.1 -> 
libint.so.1
lrwxrwxrwx root/root 0 2021-03-04 15:25 ./usr/lib/libr12-stable.so.1 -> 
libr12.so.1
lrwxrwxrwx root/root 0 2021-03-04 15:25 
./usr/lib/x86_64-linux-gnu/libderiv.so.1 -> libderiv.so.1.0.0
lrwxrwxrwx root/root 0 2021-03-04 15:25 
./usr/lib/x86_64-linux-gnu/libint.so.1 -> libint.so.1.0.0
lrwxrwxrwx root/root 0 2021-03-04 15:25 
./usr/lib/x86_64-linux-gnu/libr12.so.1 -> libr12.so.1.0.0

Do you need to move the lib*-stable.so.1 symlinks to 
/usr/lib/${DEB_HOST_MULTIARCH} ?


cheers,

Andreas


libint1_1.2.1-5.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: libint
Source-Version: 1.2.1-6
Done: Michael Banck 

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

Debian distribution maintenance software
pp.
Michael Banck  (supplier of updated libint 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: Mon, 15 Mar 2021 18:31:14 +0100
Source: libint
Architecture: source
Version: 1.2.1-6
Distribution: unstable
Urgency: medium
Maintainer: Debichem Team 
Changed-By: Michael Banck 
Closes: 985269
Changes:
 libint (1.2.1-6) unstable; urgency=medium
 .
   * debian/libint1.links: File removed.
   * debian/rules (override_dh_auto_install): New rule, runs dh_auto_install and
 then creates the lib*-stable.so.1 symlinks that were formerly handled by
 libint1.links properly in the right multiarch directory (Closes: #985269).
Checksums-Sha1:
 3f77fee78bde8ed8a9cc1e8061134c9f4067a5c0 2050 libint_1.2.1-6.dsc
 77b939097f331c7caca45c9e12e7c553fd810b8f 5208 libint_1.2.1-6.debian.tar.xz
 63b214e875cfaf29f9cfdd47c8a45c22c2c3c3d6 8477 libint_1.2.1-6_source.buildinfo
Checksums-Sha256:
 129f5e5818d8b226e89256538d7d0c56750479e919d36d909d650d42ffa69a3c 2050 
libint_1.2.1-6.dsc
 7d81350f5e5fdc147c7fa241cc7085aebeeb18548baf72348f87495f1b695c61 5208 
libint_1.2.1-6.debian.tar.xz
 cd156f8a95a1f7553dc300f95221e4365ede5df7787bd720a9d3946dc8c609e9 8477 
libint_1.2.1-6_source.buildinfo
Files:
 abd942412790ed6fc28c234ae68e5573 2050 science optional libint_1.2.1-6.dsc
 26d2d15b16dd4318a7a7dd69f7191707 5208 science optional 
libint_1.2.1-6.debian.tar.xz
 74a51014766ba50c8dda00fdceeaa03b 8477 science optional 
libint_1.2.1-6_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEnKh3dJ+rLk+paGLs3GhqJ7Q0gbAFAmBPme0ACgkQ3GhqJ7Q0
gbA1gRAApYqrFdEkw+hk+zjWjahlGz6dYdSchuL6Iu5I8LqStwkKE9oXxyatuT8F
Id104E3wRMufOSdTTem81X0fdXY7rTlTUCCi33FTpq8AdaYXxjm0llUWiOvRBlsn
gNXtxfS5Es3Isu+J3EoU/JnJuuhmFlDXVSN/jIFH0sU2q1z70i3hUsL4F2ndzaVo
24lTjH2/BRDzjhk0kPdDarxg4+oVIZMs5zNUfCzjz7TK2vsNvHTkpE1xV9FNqOSm
ER3pOi+GibE

Bug#962596: Divergence in Symantec CA blacklist reverting between sid and *stable?

[Thorsten Glaser]

Hi Julien,

>Yes, they're different.  I'm not sure what you're asking.

the reason for the difference; sorry if I was unclear.

Thanks,
//mirabilos
-- 
18:47⎜ well channels… you see, I see everything in the
same window anyway  18:48⎜ i know, you have some kind of
telnet with automatic pong 18:48⎜ haha, yes :D
18:49⎜ though that's more tinyirc – sirc is more comfy

Bug#984491: marked as done (autopkg tests fail)

[Debian Bug Tracking System]

Your message dated Mon, 15 Mar 2021 17:35:14 +
with message-id 
and subject line Bug#984491: fixed in python-furl 2.1.0-3
has caused the Debian Bug report #984491,
regarding autopkg tests fail
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.)


-- 
984491: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984491
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-furl
Version: 2.1.0-2
Severity: serious
Tags: sid bullseye

triggered by the recent python3-defaults upload, tests failing on all 
architectures:

https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-furl/10824361/log.gz

autopkgtest [08:08:01]: test unittest: [---
..F.FFF...F.
==
FAIL: test_add (tests.test_furl.TestQuery)
--
Traceback (most recent call last):
  File "/tmp/autopkgtest-lxc.0gvxgc25/downtmp/build.Mkz/src/tests/test_furl.py",
line 660, in test_add
assert q.params.allitems() == runningsum
AssertionError

==
FAIL: test_params (tests.test_furl.TestQuery)
--
Traceback (most recent call last):
  File "/tmp/autopkgtest-lxc.0gvxgc25/downtmp/build.Mkz/src/tests/test_furl.py",
line 788, in test_params
assert item1 == item2
AssertionError

==
FAIL: test_remove (tests.test_furl.TestQuery)
--
Traceback (most recent call last):
  File "/tmp/autopkgtest-lxc.0gvxgc25/downtmp/build.Mkz/src/tests/test_furl.py",
line 702, in test_remove
assert len(q.params) == 0
AssertionError

==
FAIL: test_set (tests.test_furl.TestQuery)
--
Traceback (most recent call last):
  File "/tmp/autopkgtest-lxc.0gvxgc25/downtmp/build.Mkz/src/tests/test_furl.py",
line 669, in test_set
assert q.params.allitems() == items_omd.allitems()
AssertionError

==
FAIL: test_various (tests.test_furl.TestQuery)
--
Traceback (most recent call last):
  File "/tmp/autopkgtest-lxc.0gvxgc25/downtmp/build.Mkz/src/tests/test_furl.py",
line 632, in test_various
assert q.params.allitems() == items.allitems()
AssertionError

--
Ran 76 tests in 1.357s

FAILED (failures=5)
--- End Message ---
--- Begin Message ---
Source: python-furl
Source-Version: 2.1.0-3
Done: Iñaki Malerba 

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

Debian distribution maintenance software
pp.
Iñaki Malerba  (supplier of updated python-furl 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, 15 Mar 2021 16:43:22 +0100
Source: python-furl
Architecture: source
Version: 2.1.0-3
Distribution: unstable
Urgency: medium
Maintainer: Iñaki Malerba 
Changed-By: Iñaki Malerba 
Closes: 984491
Changes:
 python-furl (2.1.0-3) unstable; urgency=medium
 .
   * Fix autopkgtests in python3.9 (Closes: #984491)
Checksums-Sha1:
 c0dba7ac4e36884a812892e6ee6c01b860225be4 1903 python-furl_2.1.0-3.dsc
 e2c39b0c538238977ea9bbfb365bd3dd34118cbc 3436 python-furl_2.1.0-3.debian.tar.xz
 82462548a0e6e509d4eaf757789a965de1e1730c 6133 
python-furl_2.1.0-3_source.buildinfo
Checksums-Sha256:
 c23f3b41707cd0b45dff2dfb70b73ed101d7f5263b8cec7ec1a831f033efaac8 1903 
python-furl_2.1.0-3.dsc
 20caae753b95fbbb6978f2d355f1c29f2aedcdd77f8049559f2cca5f4449cfea 3436 
python-furl_2.1.0-3.debian.tar.xz
 955541e3759fb71fbb18cf9915cc41211bb3c9da52fa14f0e5fca25da4887166 6133 
python-furl_2.1.0-3_source.buildi

Bug#985302: marked as done (jitterentropy-rngd uses 100% CPU on Linux >= 5.11)

[Debian Bug Tracking System]

Your message dated Mon, 15 Mar 2021 17:18:27 +
with message-id 
and subject line Bug#985302: fixed in jitterentropy-rngd 1.2.1-2
has caused the Debian Bug report #985302,
regarding jitterentropy-rngd uses 100% CPU on Linux >= 5.11
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.)


-- 
985302: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985302
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: jitterentropy-rngd
Version: 1.2.1-1
Severity: grave
Tags: patch upstream
Justification: renders package unusable

Dear Maintainer,

starting on some version of kernel 5.11, jitterentropy-rngd starts sucking
entropy rather than providing it, leading to more efforts in providing entropy, 
leading to 1 CPU being hogged up with permanent 100% utilization.

The Mobian derivative suffers from this, so we would appreciate if a fix
could still enter bullsyeye. This has been reported upstream, e.g.

https://github.com/smuellerDD/jitterentropy-rngd/issues/20
https://github.com/smuellerDD/jitterentropy-rngd/issues/19

Upstream author has provided a fix which we have tested on the pinephone and 
which indeed fixes the problem. The commit fixing this is:

https://github.com/smuellerDD/jitterentropy-rngd/commit/9227212bc50d2bfcd4ae782d068f7030a1a7cb88

I have forked the debian packaging repo, added the patch and successfully
build a new package. The MR is at:
https://salsa.debian.org/debian/jitterentropy-rngd/-/merge_requests/2

The only change I am not sure is the added entry in d/changelog, otherwise this 
is "just" adding the patch. Feel free to override the changelog modifications.

This is a grave bug once it occurs as it continually hogs up one CPU with 100%.

Thanks for considering the fix.

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-3-amd64 (SMP w/4 CPU threads)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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 jitterentropy-rngd depends on:
ii  init-system-helpers  1.60
ii  libc62.31-9

jitterentropy-rngd recommends no packages.

jitterentropy-rngd suggests no packages.
--- End Message ---
--- Begin Message ---
Source: jitterentropy-rngd
Source-Version: 1.2.1-2
Done: Luca Boccassi 

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

Debian distribution maintenance software
pp.
Luca Boccassi  (supplier of updated jitterentropy-rngd 
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, 15 Mar 2021 17:07:43 +
Source: jitterentropy-rngd
Architecture: source
Version: 1.2.1-2
Distribution: unstable
Urgency: medium
Maintainer: Luca Boccassi 
Changed-By: Luca Boccassi 
Closes: 985302
Changes:
 jitterentropy-rngd (1.2.1-2) unstable; urgency=medium
 .
   * Backport patches to fix 100% CPU usage bug when running on kernel
 5.11 or newer. (Closes: #985302)
   * Add d/upstream/metadata file
Checksums-Sha1:
 227eb00531d6aadb7632d78aeaf2b758cedd9d52 1918 jitterentropy-rngd_1.2.1-2.dsc
 e53bc9288c1ab94040a8822f10c9728d41d10826 11232 
jitterentropy-rngd_1.2.1-2.debian.tar.xz
 d4bbf04d0d70817fc7ae6da120404fa8b9956f7e 6061 
jitterentropy-rngd_1.2.1-2_source.buildinfo
Checksums-Sha256:
 344684f157c0290f4ccb102370f393a4ed5f7a9c5140c75e90e561d96bcd9e9d 1918 
jitterentropy-rngd_1.2.1-2.dsc
 af250ffe660a6ceef43e9915140192cd65480ab41933fa95d75fdaac8068ee33 11232 
jitterentropy-rngd_1.2.1-2.debian.tar.xz
 d0fde606ba13b63f9103ebbb7835f4f159de1b621c24c89811e0202638139eff 6061 
jitterentropy-rngd_1.2.1-2_source.buildinfo
Files:
 a2d7eb456baa62457c5c246f5e93ff72 1918 utils optional 
jitterentropy-rngd_1.2.1-2.dsc
 7ffbafbdf194db8d812282d9ad039984 11232 utils optional 
jitterentropy-rngd_1.2.1-2.debian.tar.xz
 fc8161c6c4f70431f5314e3462df8455 6061 utils optional 
jitterentropy-rngd_1.2.1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQFFBAEBCg

Bug#962596: [EXTERNAL] Re: Bug#962596: Backport to stretch?

[Damon Tivel]

Thanks so much, Utkarsh!

Damon

-Original Message-
From: Utkarsh Gupta  
Sent: Saturday, March 13, 2021 11:10 AM
To: Damon Tivel ; Michael Simons (.NET) 

Cc: debian-...@lists.debian.org; 962...@bugs.debian.org; Jon Douglas 

Subject: [EXTERNAL] Re: Bug#962596: Backport to stretch?

Hi Damon, Michael,

On Sat, Mar 13, 2021 at 9:55 PM Utkarsh Gupta  wrote:
> So the upload should happen by this weekend!

This fix has now been patched, uploaded, accepted, and announced[1].
[1]: 
https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.debian.org%2Fdebian-lts-announce%2F2021%2F03%2Fmsg00016.html&data=04%7C01%7Cdtivel%40microsoft.com%7Cb5a86e2948784d65470108d8e653b8c6%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637512594848578747%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=H%2BKizOZq2OXLdWF6H4F1x3vAzu8C385ScPXnq0fnqzQ%3D&reserved=0

This also means that the G/H issue
(https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FNuGet%2FAnnouncements%2Fissues%2F49&data=04%7C01%7Cdtivel%40microsoft.com%7Cb5a86e2948784d65470108d8e653b8c6%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637512594848578747%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=FcWcz%2FigjEKS7CFn%2F60KVCsu8HRait8YELkKDvXW0%2Bw%3D&reserved=0)
 can now be updated to mark Debian 9 ("stretch") as resolved. Should you need 
any more information or help with this, please let me know.


- u

Processed: severity of 982552 is grave

[Debian Bug Tracking System]

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

> severity 982552 grave
Bug #982552 [src:ruby-carrierwave] ruby-carrierwave: CVE-2021-21288
Ignoring request to change severity of Bug 982552 to the same value.
> thanks
Stopping processing here.

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

Bug#985087: marked as done (CVE-2021-27378)

[Debian Bug Tracking System]

Your message dated Mon, 15 Mar 2021 15:58:56 +
with message-id 
and subject line re: CVE-2021-27378
has caused the Debian Bug report #985087,
regarding CVE-2021-27378
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.)


-- 
985087: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985087
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-rand-core
Severity: grave
Tags: security
X-Debbugs-Cc: Debian Security Team 

Please see:
https://rustsec.org/advisories/RUSTSEC-2021-0023.html

Cheers,
Moritz
--- End Message ---
--- Begin Message ---

> At first sight it appears to me that version 0.5.1 does not have the issue,
> but I'd prefer to have that checked by more eyes.

I have looked and agree with your analysis, I also asked upstream and they
also agree.

Therefore I am closing this bug.--- End Message ---

Processed: severity of 982552 is grave

[Debian Bug Tracking System]

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

> severity 982552 grave
Bug #982552 [src:ruby-carrierwave] ruby-carrierwave: CVE-2021-21288
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

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

Bug#985142: marked as done (chromium: CVE-2021-21193 (RCE) in Blink)

[Debian Bug Tracking System]

Your message dated Mon, 15 Mar 2021 15:49:18 +
with message-id 
and subject line Bug#985142: fixed in chromium 89.0.4389.90-1
has caused the Debian Bug report #985142,
regarding chromium: CVE-2021-21193 (RCE) in Blink
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.)


-- 
985142: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985142
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: chromium
Version: 89.0.4389.82-1
Severity: grave
Tags: upstream security
Justification: user security hole
X-Debbugs-Cc: aeru...@aerusso.net, Debian Security Team 


Per [1] (or [2], and allegedly [3] which I cannot access):

> A use after free security issue was found in the Blink component of the
> Chromium browser before version 89.0.4389.90. Google is aware of reports
> that an exploit for this issue exists in the wild.

Does this also affect libqt5webengine5?  I know that its upstream derives
in part from the Chromium source tree.

Antonio

[1] 
https://chromereleases.googleblog.com/2021/03/stable-channel-update-for-desktop_12.html
[2] https://security.archlinux.org/CVE-2021-21193
[3] https://crbug.com/1186287


OpenPGP_0xB01C53D5DED4A4EE.asc
Description: application/pgp-keys


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: chromium
Source-Version: 89.0.4389.90-1
Done: Michel Le Bihan 

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

Debian distribution maintenance software
pp.
Michel Le Bihan  (supplier of updated chromium 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, 15 Mar 2021 12:57:00 +0100
Source: chromium
Architecture: source
Version: 89.0.4389.90-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Chromium Team 
Changed-By: Michel Le Bihan 
Closes: 984926 985142 985271
Changes:
 chromium (89.0.4389.90-1) unstable; urgency=medium
 .
   * New upstream security release (closes: #985271).
 - CVE-2021-21191: Use after free in WebRTC. Reported by raven @raid_akame
 - CVE-2021-21192: Heap buffer overflow in tab groups. Reported by
   Abdulrahman Alqabandi, Microsoft Browser Vulnerability Research
 - CVE-2021-21193: Use after free in Blink. Reported by Anonymous
   (closes: #985142)
   * Fix build with libvpx 1.7.0 and libicu63 (closes: #984926).
   * Change debian/rules to not leave debian/scripts/mk-origtargz
Checksums-Sha1:
 aafb466a863c483b9bca0499e4cf10ca635941cd 3639 chromium_89.0.4389.90-1.dsc
 e3617eeddf4ff5b4c3cf1c2f25a1efc1a9fc990f 427206432 
chromium_89.0.4389.90.orig.tar.xz
 cd245ccd72a533631949406a0fda536fe6697bb5 210592 
chromium_89.0.4389.90-1.debian.tar.xz
 9e0ecf51d18d414eb6582c483e48f14f6101d7c6 14738 
chromium_89.0.4389.90-1_source.buildinfo
Checksums-Sha256:
 512d90f02e6af04019a9271180a49ef9f5690b1fe2db2f25c69d99ae00e647c0 3639 
chromium_89.0.4389.90-1.dsc
 c0b9f344749d43cb700d771d3d4c7f041186acc264d779bd8157e98d9aff68f5 427206432 
chromium_89.0.4389.90.orig.tar.xz
 67a129dc9112ce92a1498da370f8c9b3c470835e442ed3a51c0619c2d219ef7c 210592 
chromium_89.0.4389.90-1.debian.tar.xz
 823a040fb48861ca2e37c7fe1a0132763fd46f3d8c2407a1840a7dff005a18c8 14738 
chromium_89.0.4389.90-1_source.buildinfo
Files:
 242ea3437490fbbf08f1e8ae8fa2ecb8 3639 web optional chromium_89.0.4389.90-1.dsc
 e73b69040e219e40d8e9f89119e554b2 427206432 web optional 
chromium_89.0.4389.90.orig.tar.xz
 b1bdf4b7144ccca1bb85dd801260bbfe 210592 web optional 
chromium_89.0.4389.90-1.debian.tar.xz
 9a3a3f838e1987ff2db5fe8d1f804ced 14738 web optional 
chromium_89.0.4389.90-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEi3hoeGwz5cZMTQpICBa54Yx2K60FAmBPfv8ACgkQCBa54Yx2
K629Jg/9EC4ir4Ds408AAbaunD/APqi9X/G3kRAd6nBIPz7Pw8lll9ESCxuFKTt+
hf8rbPb9OQISYX5tSQSt1OtqqiDldFBXgQEPr/Eo7VwqD7it5kynpBUruLs54VKe
9lp7AiyIfXQU0O90dB8nPGCh8Mwyau5FYN4V9Dxn2n6qYinahYnUnLBEb+yi6L9F
2pTwxhb0JkwpHJF3y21k6H8VoPrxQUMwkl5Yix6R9OsItyfDX1daUB94rjZwWD5w
1CAOqPitIsc7xKl8zOlCjeXoDuf61AZqfbHr/KpbGxkvsiTT08WXBfAUrrfPeNOw
jh5J81oPo9BEyPTJuSXyiX1XrnYT6oXgdJpdxCWUK

Bug#985302: jitterentropy-rngd uses 100% CPU on Linux >= 5.11

[Sebastian Spaeth]

Package: jitterentropy-rngd
Version: 1.2.1-1
Severity: grave
Tags: patch upstream
Justification: renders package unusable

Dear Maintainer,

starting on some version of kernel 5.11, jitterentropy-rngd starts sucking
entropy rather than providing it, leading to more efforts in providing entropy, 
leading to 1 CPU being hogged up with permanent 100% utilization.

The Mobian derivative suffers from this, so we would appreciate if a fix
could still enter bullsyeye. This has been reported upstream, e.g.

https://github.com/smuellerDD/jitterentropy-rngd/issues/20
https://github.com/smuellerDD/jitterentropy-rngd/issues/19

Upstream author has provided a fix which we have tested on the pinephone and 
which indeed fixes the problem. The commit fixing this is:

https://github.com/smuellerDD/jitterentropy-rngd/commit/9227212bc50d2bfcd4ae782d068f7030a1a7cb88

I have forked the debian packaging repo, added the patch and successfully
build a new package. The MR is at:
https://salsa.debian.org/debian/jitterentropy-rngd/-/merge_requests/2

The only change I am not sure is the added entry in d/changelog, otherwise this 
is "just" adding the patch. Feel free to override the changelog modifications.

This is a grave bug once it occurs as it continually hogs up one CPU with 100%.

Thanks for considering the fix.

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-3-amd64 (SMP w/4 CPU threads)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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 jitterentropy-rngd depends on:
ii  init-system-helpers  1.60
ii  libc62.31-9

jitterentropy-rngd recommends no packages.

jitterentropy-rngd suggests no packages.

Bug#985287: marked as done (nagvis: unhandled symlink to directory conversion: /usr/share/nagvis/share/server/core/ext/php-gettext-1.0.12 -> ../../../../../php/php-php-gettext)

[Debian Bug Tracking System]

Your message dated Mon, 15 Mar 2021 14:22:22 +
with message-id 
and subject line Bug#985287: fixed in nagvis 1:1.9.25-2
has caused the Debian Bug report #985287,
regarding nagvis: unhandled symlink to directory conversion: 
/usr/share/nagvis/share/server/core/ext/php-gettext-1.0.12 -> 
../../../../../php/php-php-gettext
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.)


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

Hi,

an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.

This was observed on the following upgrade paths:

  buster -> bullseye

For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#copyright-information

For other overwritten locations anything interesting may happen.

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#details-of-unpack-phase-of-installation-or-upgrade

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


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

2m15.1s ERROR: FAIL: silently overwrites files via directory symlinks:
  /usr/share/nagvis/share/server/core/ext/php-gettext-1.0.12/AUTHORS (nagvis) 
!= /usr/share/php/php-php-gettext/AUTHORS (?)
/usr/share/nagvis/share/server/core/ext/php-gettext-1.0.12 -> 
../../../../../php/php-php-gettext
  /usr/share/nagvis/share/server/core/ext/php-gettext-1.0.12/COPYING (nagvis) 
!= /usr/share/php/php-php-gettext/COPYING (?)
/usr/share/nagvis/share/server/core/ext/php-gettext-1.0.12 -> 
../../../../../php/php-php-gettext
  /usr/share/nagvis/share/server/core/ext/php-gettext-1.0.12/README (nagvis) != 
/usr/share/php/php-php-gettext/README (?)
/usr/share/nagvis/share/server/core/ext/php-gettext-1.0.12 -> 
../../../../../php/php-php-gettext
  /usr/share/nagvis/share/server/core/ext/php-gettext-1.0.12/gettext.inc 
(nagvis) != /usr/share/php/php-php-gettext/gettext.inc (php-php-gettext)
/usr/share/nagvis/share/server/core/ext/php-gettext-1.0.12 -> 
../../../../../php/php-php-gettext
  /usr/share/nagvis/share/server/core/ext/php-gettext-1.0.12/gettext.php 
(nagvis) != /usr/share/php/php-php-gettext/gettext.php (php-php-gettext)
/usr/share/nagvis/share/server/core/ext/php-gettext-1.0.12 -> 
../../../../../php/php-php-gettext
  /usr/share/nagvis/share/server/core/ext/php-gettext-1.0.12/streams.php 
(nagvis) != /usr/share/php/php-php-gettext/streams.php (php-php-gettext)
/usr/share/nagvis/share/server/core/ext/php-gettext-1.0.12 -> 
../../../../../php/php-php-gettext


cheers,

Andreas


nagvis_1:1.9.25-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: nagvis
Source-Version: 1:1.9.25-2
Done: Bas Couwenberg 

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

Debian distribution maintenance software
pp.
Bas Couwenberg  (supplier of updated nagvis 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: 

Bug#985297: libreoffice-common: needs Conflicts against all packages shipping files in /usr/lib/libreoffice/share/registry

[Andreas Beckmann]

Package: libreoffice-common
Version: 1:7.0.4-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + libreoffice-writer libreoffice-draw libreoffice-calc 
libreoffice-base libreoffice-math

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'buster'.
It installed fine in 'buster', then the upgrade to 'bullseye' fails.

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

  Preparing to unpack .../0-ure_1%3a7.0.4-3_amd64.deb ...
  Unpacking ure (1:7.0.4-3) over (6.1.5-3+deb10u7) ...
  Preparing to unpack .../1-libreoffice-style-colibre_1%3a7.0.4-3_all.deb ...
  Unpacking libreoffice-style-colibre (1:7.0.4-3) over (1:6.1.5-3+deb10u7) ...
  dpkg: considering deconfiguration of libreoffice-writer, which would be 
broken by installation of libreoffice-core ...
  dpkg: yes, will deconfigure libreoffice-writer (broken by libreoffice-core)
  Preparing to unpack .../2-libreoffice-core_1%3a7.0.4-3_amd64.deb ...
  De-configuring libreoffice-writer (1:6.1.5-3+deb10u7) ...
  Unpacking libreoffice-core (1:7.0.4-3) over (1:6.1.5-3+deb10u7) ...
  dpkg: considering removing libreoffice-writer in favour of libreoffice-common 
...
  dpkg: libreoffice-writer is not properly installed; ignoring any dependencies 
on it
  dpkg: yes, will remove libreoffice-writer in favour of libreoffice-common
  Preparing to unpack .../3-libreoffice-common_1%3a7.0.4-3_all.deb ...
  dpkg-maintscript-helper: error: file 
'/usr/lib/libreoffice/share/registry/writer.xcd' not owned by package 
'libreoffice-common:all'
  dpkg-maintscript-helper: error: directory 
'/usr/lib/libreoffice/share/registry' contains files not owned by package 
libreoffice-common:all, cannot switch to symlink
  dpkg: error processing archive 
/tmp/apt-dpkg-install-sERX6l/3-libreoffice-common_1%3a7.0.4-3_all.deb 
(--unpack):
   new libreoffice-common package pre-installation script subprocess returned 
error exit status 1
  rmdir: failed to remove '/var/lib/libreoffice/program/': No such file or 
directory
  rmdir: failed to remove '/var/lib/libreoffice': No such file or directory
  Selecting previously unselected package libreoffice-writer.
  dpkg: considering deconfiguration of libreoffice-common, which would be 
broken by installation of libreoffice-writer ...
  dpkg: yes, will deconfigure libreoffice-common (broken by libreoffice-writer)
  Preparing to unpack .../4-libreoffice-writer_1%3a7.0.4-3_amd64.deb ...
  De-configuring libreoffice-common (1:6.1.5-3+deb10u7) ...
  Unpacking libreoffice-writer (1:7.0.4-3) over (1:6.1.5-3+deb10u7) ...
  Replacing files in old package libreoffice-common (1:6.1.5-3+deb10u7) ...
  Preparing to unpack .../5-libxmlsec1_1.2.31-1_amd64.deb ...
  Unpacking libxmlsec1:amd64 (1.2.31-1) over (1.2.27-2) ...
  Preparing to unpack .../6-libreoffice-base-core_1%3a7.0.4-3_amd64.deb ...
  Unpacking libreoffice-base-core (1:7.0.4-3) over (1:6.1.5-3+deb10u7) ...
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-sERX6l/3-libreoffice-common_1%3a7.0.4-3_all.deb

You already have all the needed Conflicts ...

In this complicated upgrade case I don't see a solution to get
dpkg-maintscript-helper dir_to_symlink to work properly ...

Therefore I'd suggest to not use dir_to_symlink here ... but to
fixup the link in postinst configure:

if [ ! -L /usr/lib/libreoffice/share/registry ]; then
if [ -d /usr/lib/libreoffice/share/registry ]; then
# this will fail if the directory is not yet empty
rmdir /usr/lib/libreoffice/share/registry
fi
ln -s /etc/libreoffice/registry /usr/lib/libreoffice/share/registry
fi

I would actually go for the fail-if-not-empty case and fix up all the
upgrade paths triggering this.


cheers,

Andreas

PS: for a log time I thought this was just another bug caused by dpkg bug 
#983855
but I'm now using a patched dpkg in my piuparts instance ...


libreoffice-writer_1:7.0.4-3.log.gz
Description: application/gzip

Processed: libreoffice-common: needs Conflicts against all packages shipping files in /usr/lib/libreoffice/share/registry

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + libreoffice-writer libreoffice-draw libreoffice-calc 
> libreoffice-base libreoffice-math
Bug #985297 [libreoffice-common] libreoffice-common: needs Conflicts against 
all packages shipping files in /usr/lib/libreoffice/share/registry
Added indication that 985297 affects libreoffice-writer, libreoffice-draw, 
libreoffice-calc, libreoffice-base, and libreoffice-math

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

Bug#962596: Divergence in Symantec CA blacklist reverting between sid and *stable?

[Julien Cristau]

On Sat, Mar 13, 2021 at 08:32:32PM +, Thorsten Glaser wrote:
> Hi,
> 
> the changelogs seem to differ in re-added certificates:
> 
Yes, they're different.  I'm not sure what you're asking.

Cheers,
Julien

Processed: Bug#985269 marked as pending in libint

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #985269 [libint1] libint1: ships broken library symlinks: 
/usr/lib/lib*-stable.so.1 -> lib*.so.1
Added tag(s) pending.

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

Bug#985269: marked as pending in libint

[Michael Banck]

Control: tag -1 pending

Hello,

Bug #985269 in libint 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/debichem-team/libint/-/commit/a5933f8651c6e4ced79ceb31624dca1b89c42fc7


* debian/libint1.links: File removed.
  * debian/rules (override_dh_auto_install): New rule, runs dh_auto_install and
then creates the lib*-stable.so.1 symlinks that were formerly handled by
libint1.links properly in the right multiarch directory (Closes: #985269).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/985269

Bug#985295: qbs-examples: unhandled symlink to directory conversion: /usr/share/qbs/examples/cocoa-application/CocoaApplication/en_US.lproj -> en.lproj

[Andreas Beckmann]

Package: qbs-examples
Version: 1.18.0-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.

This was observed on the following upgrade paths:

  buster -> bullseye

For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#copyright-information

For other overwritten locations anything interesting may happen.

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#details-of-unpack-phase-of-installation-or-upgrade

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


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

  Preparing to unpack .../qbs-examples_1.18.0-4_all.deb ...
  Unpacking qbs-examples (1.18.0-4) over (1.12.2+dfsg-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/qbs-examples_1.18.0-4_all.deb (--unpack):
   unable to install new version of 
'/usr/share/qbs/examples/cocoa-application/CocoaApplication/en_US.lproj/Credits.rtf':
 No such file or directory
  Errors were encountered while processing:
   /var/cache/apt/archives/qbs-examples_1.18.0-4_all.deb


In buster /usr/share/qbs/examples/cocoa-application/CocoaApplication/en_US.lproj
was a symlink to en.lproj.

cheers,

Andreas


qbs-examples_1.18.0-4.log.gz
Description: application/gzip

Bug#985288: marked as done (chai: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE)

[Debian Bug Tracking System]

Your message dated Mon, 15 Mar 2021 13:20:01 +
with message-id 
and subject line Bug#985288: fixed in node-chai 4.2.0+ds+~4.2.14-4
has caused the Debian Bug report #985288,
regarding chai: unhandled symlink to directory conversion: 
/usr/share/doc/PACKAGE
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.)


-- 
985288: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985288
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: chai
Version: 4.2.0+ds+~4.2.14-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.

This was observed on the following upgrade paths:

  buster -> bullseye

For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#copyright-information

For other overwritten locations anything interesting may happen.

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#details-of-unpack-phase-of-installation-or-upgrade

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


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

0m40.7s ERROR: FAIL: silently overwrites files via directory symlinks:
  /usr/share/doc/chai/History.md.gz (chai) != 
/usr/share/doc/libjs-chai/History.md.gz (libjs-chai)
/usr/share/doc/chai -> libjs-chai
  /usr/share/doc/chai/changelog.Debian.gz (chai) != 
/usr/share/doc/libjs-chai/changelog.Debian.gz (libjs-chai)
/usr/share/doc/chai -> libjs-chai
  /usr/share/doc/chai/changelog.gz (chai) != 
/usr/share/doc/libjs-chai/changelog.gz (libjs-chai)
/usr/share/doc/chai -> libjs-chai
  /usr/share/doc/chai/copyright (chai) != /usr/share/doc/libjs-chai/copyright 
(libjs-chai)
/usr/share/doc/chai -> libjs-chai


cheers,

Andreas


chai_4.2.0+ds+~4.2.14-3.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: node-chai
Source-Version: 4.2.0+ds+~4.2.14-4
Done: Yadd 

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

Debian distribution maintenance software
pp.
Yadd  (supplier of updated node-chai 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, 15 Mar 2021 13:56:47 +0100
Source: node-chai
Architecture: source
Version: 4.2.0+ds+~4.2.14-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Yadd 
Closes: 985288
Changes:
 node-chai (4.2.0+ds+~4.2.14-4) unstable; urgency=medium
 .
   * Team upload
   * Fix maintscript (Closes: #985288)
Checksums-Sha1: 
 c9f437f0f1ac069d303cf461e84bddcdae3a657c 2616 node-chai_4.2.0+ds+~4.2.14-4.dsc
 f57baaebf4b6931969b3a42b9c3cd589e5cfe6a5 7316 
node-chai_4.2.0+ds+~4.2.14-4.debian.tar.xz
Checksums-Sha256: 
 fda47f47417ff71056cf105b18402e304604a83aa52684e6ca8ebc669df5fd1d 2616 
node-chai_4.2.0+ds+~4.2.14-4.dsc
 8145e08118c159ec8f8fdc3db8b6f01f8f058a2dde8688c6a7d70344af2451a7 7316 
node-chai_4.2.0+ds+~4.2.14-4.debian.tar.xz
Files: 
 ab9460dc24f5cb6a379b390b30248a73 2616 javascript optional 
node-chai_4.2.0+ds+~4.2.14-4.dsc
 59a4ed987a2c5acfc89dd77600a75351 7316 javascript optional 
n

Bug#985288: [Pkg-javascript-devel] Bug#985288: chai: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

[Yadd]

Le 15/03/2021 à 13:30, Andreas Beckmann a écrit :
> Package: chai
> Version: 4.2.0+ds+~4.2.14-3
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
> 
> Hi,
> 
> an upgrade test with piuparts revealed that your package installs files
> over existing symlinks and possibly overwrites files owned by other
> packages. This usually means an old version of the package shipped a
> symlink but that was later replaced by a real (and non-empty)
> directory. This kind of overwriting another package's files cannot be
> detected by dpkg.
> 
> This was observed on the following upgrade paths:
> 
>   buster -> bullseye
> 
> For /usr/share/doc/PACKAGE this may not be problematic as long as both
> packages are installed, ship byte-for-byte identical files and are
> upgraded in lockstep. But once one of the involved packages gets
> removed, the other one will lose its documentation files, too,
> including the copyright file, which is a violation of Policy 12.5:
> https://www.debian.org/doc/debian-policy/ch-docs.html#copyright-information
> 
> For other overwritten locations anything interesting may happen.
> 
> Note that dpkg intentionally does not replace directories with symlinks
> and vice versa, you need the maintainer scripts to do this.
> See in particular the end of point 4 in
> https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#details-of-unpack-phase-of-installation-or-upgrade
> 
> It is recommended to use the dpkg-maintscript-helper commands
> 'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
> to perform the conversion, ideally using d/$PACKAGE.maintscript.
> See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.
> 
> 
> From the attached log (scroll to the bottom...):
> 
> 0m40.7s ERROR: FAIL: silently overwrites files via directory symlinks:
>   /usr/share/doc/chai/History.md.gz (chai) != 
> /usr/share/doc/libjs-chai/History.md.gz (libjs-chai)
> /usr/share/doc/chai -> libjs-chai
>   /usr/share/doc/chai/changelog.Debian.gz (chai) != 
> /usr/share/doc/libjs-chai/changelog.Debian.gz (libjs-chai)
> /usr/share/doc/chai -> libjs-chai
>   /usr/share/doc/chai/changelog.gz (chai) != 
> /usr/share/doc/libjs-chai/changelog.gz (libjs-chai)
> /usr/share/doc/chai -> libjs-chai
>   /usr/share/doc/chai/copyright (chai) != /usr/share/doc/libjs-chai/copyright 
> (libjs-chai)
> /usr/share/doc/chai -> libjs-chai

Hi,

there is already a maintscript for this:

  $ cat debian/chai.maintscript
  dir_to_symlink /usr/share/doc/chai libjs-chai 4.2.0+ds-2~

What is wrong here ?

Bug#985288: [Pkg-javascript-devel] Bug#985288: chai: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

[Yadd]

Le 15/03/2021 à 13:49, Yadd a écrit :
> Le 15/03/2021 à 13:30, Andreas Beckmann a écrit :
>> Package: chai
>> Version: 4.2.0+ds+~4.2.14-3
>> Severity: serious
>> User: debian...@lists.debian.org
>> Usertags: piuparts
>>
>> Hi,
>>
>> an upgrade test with piuparts revealed that your package installs files
>> over existing symlinks and possibly overwrites files owned by other
>> packages. This usually means an old version of the package shipped a
>> symlink but that was later replaced by a real (and non-empty)
>> directory. This kind of overwriting another package's files cannot be
>> detected by dpkg.
>>
>> This was observed on the following upgrade paths:
>>
>>   buster -> bullseye
>>
>> For /usr/share/doc/PACKAGE this may not be problematic as long as both
>> packages are installed, ship byte-for-byte identical files and are
>> upgraded in lockstep. But once one of the involved packages gets
>> removed, the other one will lose its documentation files, too,
>> including the copyright file, which is a violation of Policy 12.5:
>> https://www.debian.org/doc/debian-policy/ch-docs.html#copyright-information
>>
>> For other overwritten locations anything interesting may happen.
>>
>> Note that dpkg intentionally does not replace directories with symlinks
>> and vice versa, you need the maintainer scripts to do this.
>> See in particular the end of point 4 in
>> https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#details-of-unpack-phase-of-installation-or-upgrade
>>
>> It is recommended to use the dpkg-maintscript-helper commands
>> 'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
>> to perform the conversion, ideally using d/$PACKAGE.maintscript.
>> See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.
>>
>>
>> From the attached log (scroll to the bottom...):
>>
>> 0m40.7s ERROR: FAIL: silently overwrites files via directory symlinks:
>>   /usr/share/doc/chai/History.md.gz (chai) != 
>> /usr/share/doc/libjs-chai/History.md.gz (libjs-chai)
>> /usr/share/doc/chai -> libjs-chai
>>   /usr/share/doc/chai/changelog.Debian.gz (chai) != 
>> /usr/share/doc/libjs-chai/changelog.Debian.gz (libjs-chai)
>> /usr/share/doc/chai -> libjs-chai
>>   /usr/share/doc/chai/changelog.gz (chai) != 
>> /usr/share/doc/libjs-chai/changelog.gz (libjs-chai)
>> /usr/share/doc/chai -> libjs-chai
>>   /usr/share/doc/chai/copyright (chai) != 
>> /usr/share/doc/libjs-chai/copyright (libjs-chai)
>> /usr/share/doc/chai -> libjs-chai
> 
> Hi,
> 
> there is already a maintscript for this:
> 
>   $ cat debian/chai.maintscript
>   dir_to_symlink /usr/share/doc/chai libjs-chai 4.2.0+ds-2~
> 
> What is wrong here ?

Found: s/dir_to_symlink/symlink_to_dir/ :-(

Bug#985293: neutron-common: missing Breaks: python3-neutron-fwaas

[Andreas Beckmann]

Package: neutron-common
Version: 2:17.1.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + python3-neutron-fwaas

Hi,

during a test with piuparts I noticed python3-neutron-fwaas fails to
remove after the upgrade from buster to bullseye.

python3-neutron-fwaas does not exist in bullseye any longer, but does
not get removed during the upgrade. Removing the package after the
upgrade fails because it calls neutron-plugin-manage in a now
unsupported way. At least that's what I conclude from the log.

Adding a (unversioned) Breaks against the package should get it
removed before the incompatible neutron-plugin-manage script gets
unpacked.

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

  Removing python3-neutron-fwaas (1:13.0.1-7) ...
  2021-03-13 21:36:47,852 - stevedore.extension - ERROR - Could not load 
'firewall': cannot import name 'rpc' from 'neutron.common' 
(/usr/lib/python3/dist-packages/neutron/common/__init__.py)
  2021-03-13 21:36:47,869 - stevedore.extension - ERROR - Could not load 
'firewall_v2': cannot import name '_model_query' from 'neutron.db' 
(/usr/lib/python3/dist-packages/neutron/db/__init__.py)
  2021-03-13 21:36:47,870 - stevedore.extension - ERROR - Could not load 
'neutron.services.firewall.fwaas_plugin.FirewallPlugin': cannot import name 
'rpc' from 'neutron.common' 
(/usr/lib/python3/dist-packages/neutron/common/__init__.py)
  2021-03-13 21:36:47,883 - stevedore.extension - ERROR - Could not load 
'fwaas': cannot import name 'rpc' from 'neutron.common' 
(/usr/lib/python3/dist-packages/neutron/common/__init__.py)
  2021-03-13 21:36:47,886 - stevedore.extension - ERROR - Could not load 
'fwaas_v2': cannot import name 'rpc' from 'neutron.common' 
(/usr/lib/python3/dist-packages/neutron/common/__init__.py)
  2021-03-13 21:36:47,915 - neutron-plugin-manage - ERROR - Could not load 
'neutron.fwaas': cannot import name 'rpc' from 'neutron.common' 
(/usr/lib/python3/dist-packages/neutron/common/__init__.py)
  usage: neutron-plugin-manage disable
 [-h]
 [--service-plugin 
{auto_allocate,conntrack_helper,dummy,flavors,log,loki,metering,network_ip_availability,network_segment_range,ovn-router,placement,port_forwarding,qos,revisions,router,segments,tag,timestamp,trunk}]
 [--l3-extension 
{conntrack_helper,fip_qos,gateway_ip_qos,port_forwarding,snat_log,fwaas_v2_log}]
 {enable,disable}
 ...
  neutron-plugin-manage disable: error: argument --service-plugin: invalid 
choice: 'firewall_v2' (choose from 'auto_allocate', 'conntrack_helper', 
'dummy', 'flavors', 'log', 'loki', 'metering', 'network_ip_availability', 
'network_segment_range', 'ovn-router', 'placement', 'port_forwarding', 'qos', 
'revisions', 'router', 'segments', 'tag', 'timestamp', 'trunk')
  dpkg: error processing package python3-neutron-fwaas (--remove):
   installed python3-neutron-fwaas package pre-removal script subprocess 
returned error exit status 2
  dpkg: too many errors, stopping
  Errors were encountered while processing:
   python3-neutron-fwaas


cheers,

Andreas


python3-neutron-fwaas_None.log.gz
Description: application/gzip

Processed: neutron-common: missing Breaks: python3-neutron-fwaas

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + python3-neutron-fwaas
Bug #985293 [neutron-common] neutron-common: missing Breaks: 
python3-neutron-fwaas
Added indication that 985293 affects python3-neutron-fwaas

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

Bug#985292: materia-gtk-theme: unhandled symlink to directory conversion: /usr/share/themes/Materia-compact/gtk-3.0/assets -> ../gtk-assets

[Andreas Beckmann]

Package: materia-gtk-theme
Version: 20200916-0.1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.

This was observed on the following upgrade paths:

  buster -> bullseye

For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#copyright-information

For other overwritten locations anything interesting may happen.

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#details-of-unpack-phase-of-installation-or-upgrade

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


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

1m8.4s ERROR: installs objects over existing directory symlinks:
  
/usr/share/themes/Materia-compact/gtk-3.0/assets/scale-horz-marks-after-slider-dark.png
 (materia-gtk-theme) != 
/usr/share/themes/Materia-compact/gtk-assets/scale-horz-marks-after-slider-dark.png
 (?)
/usr/share/themes/Materia-compact/gtk-3.0/assets -> ../gtk-assets
  
/usr/share/themes/Materia-compact/gtk-3.0/assets/scale-horz-marks-after-slider-d...@2.png
 (materia-gtk-theme) != 
/usr/share/themes/Materia-compact/gtk-assets/scale-horz-marks-after-slider-d...@2.png
 (?)
/usr/share/themes/Materia-compact/gtk-3.0/assets -> ../gtk-assets
  
/usr/share/themes/Materia-compact/gtk-3.0/assets/scale-horz-marks-after-slider-disabled-dark.png
 (materia-gtk-theme) != 
/usr/share/themes/Materia-compact/gtk-assets/scale-horz-marks-after-slider-disabled-dark.png
 (?)
/usr/share/themes/Materia-compact/gtk-3.0/assets -> ../gtk-assets
  
/usr/share/themes/Materia-compact/gtk-3.0/assets/scale-horz-marks-after-slider-disabled-d...@2.png
 (materia-gtk-theme) != 
/usr/share/themes/Materia-compact/gtk-assets/scale-horz-marks-after-slider-disabled-d...@2.png
 (?)
/usr/share/themes/Materia-compact/gtk-3.0/assets -> ../gtk-assets
  
/usr/share/themes/Materia-compact/gtk-3.0/assets/scale-horz-marks-after-slider-disabled.png
 (materia-gtk-theme) != 
/usr/share/themes/Materia-compact/gtk-assets/scale-horz-marks-after-slider-disabled.png
 (?)
/usr/share/themes/Materia-compact/gtk-3.0/assets -> ../gtk-assets
[...]
  
/usr/share/themes/Materia/gtk-3.0/assets/selectionmode-checkbox-unchecked-d...@2.png
 (materia-gtk-theme) != 
/usr/share/themes/Materia/gtk-assets/selectionmode-checkbox-unchecked-d...@2.png
 (?)
/usr/share/themes/Materia/gtk-3.0/assets -> ../gtk-assets
  /usr/share/themes/Materia/gtk-3.0/assets/selectionmode-checkbox-unchecked.png 
(materia-gtk-theme) != 
/usr/share/themes/Materia/gtk-assets/selectionmode-checkbox-unchecked.png (?)
/usr/share/themes/Materia/gtk-3.0/assets -> ../gtk-assets
  
/usr/share/themes/Materia/gtk-3.0/assets/selectionmode-checkbox-unchec...@2.png 
(materia-gtk-theme) != 
/usr/share/themes/Materia/gtk-assets/selectionmode-checkbox-unchec...@2.png (?)
/usr/share/themes/Materia/gtk-3.0/assets -> ../gtk-assets


cheers,

Andreas


materia-gtk-theme_20200916-0.1.log.gz
Description: application/gzip

Bug#985290: libxdffileio-dev: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

[Andreas Beckmann]

Package: libxdffileio-dev
Version: 0.3-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.

This was observed on the following upgrade paths:

  buster -> bullseye

For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#copyright-information

For other overwritten locations anything interesting may happen.

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#details-of-unpack-phase-of-installation-or-upgrade

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


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

0m34.4s ERROR: FAIL: silently overwrites files via directory symlinks:
  /usr/share/doc/libxdffileio-dev/changelog.Debian.gz (libxdffileio-dev:amd64) 
!= /usr/share/doc/libxdffileio0/changelog.Debian.gz (libxdffileio0:amd64)
/usr/share/doc/libxdffileio-dev -> libxdffileio0
  /usr/share/doc/libxdffileio-dev/changelog.gz (libxdffileio-dev:amd64) != 
/usr/share/doc/libxdffileio0/changelog.gz (libxdffileio0:amd64)
/usr/share/doc/libxdffileio-dev -> libxdffileio0
  /usr/share/doc/libxdffileio-dev/copyright (libxdffileio-dev:amd64) != 
/usr/share/doc/libxdffileio0/copyright (libxdffileio0:amd64)
/usr/share/doc/libxdffileio-dev -> libxdffileio0
  /usr/share/doc/libxdffileio-dev/example (libxdffileio-dev:amd64) != 
/usr/share/doc/libxdffileio0/example (?)
/usr/share/doc/libxdffileio-dev -> libxdffileio0
  /usr/share/doc/libxdffileio-dev/example/Makefile (libxdffileio-dev:amd64) != 
/usr/share/doc/libxdffileio0/example/Makefile (?)
/usr/share/doc/libxdffileio-dev -> libxdffileio0
  /usr/share/doc/libxdffileio-dev/example/copy_datafile.c.gz 
(libxdffileio-dev:amd64) != 
/usr/share/doc/libxdffileio0/example/copy_datafile.c.gz (?)
/usr/share/doc/libxdffileio-dev -> libxdffileio0
  /usr/share/doc/libxdffileio-dev/example/create_bdf.c.gz 
(libxdffileio-dev:amd64) != 
/usr/share/doc/libxdffileio0/example/create_bdf.c.gz (?)
/usr/share/doc/libxdffileio-dev -> libxdffileio0


cheers,

Andreas


libxdffileio-dev_0.3-3.log.gz
Description: application/gzip

Bug#985289: flamerobin: unhandled symlink to directory conversion: /usr/share/doc/flamerobin/html -> ../../flamerobin/docs

[Andreas Beckmann]

Package: flamerobin
Version: 0.9.3.6-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.

This was observed on the following upgrade paths:

  buster -> bullseye

For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#copyright-information

For other overwritten locations anything interesting may happen.

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#details-of-unpack-phase-of-installation-or-upgrade

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


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

1m18.5s ERROR: installs objects over existing directory symlinks:
  /usr/share/doc/flamerobin/html/fr_license.html (flamerobin) != 
/usr/share/flamerobin/docs/fr_license.html (?)
/usr/share/doc/flamerobin/html -> ../../flamerobin/docs
  /usr/share/doc/flamerobin/html/fr_whatsnew.html (flamerobin) != 
/usr/share/flamerobin/docs/fr_whatsnew.html (?)
/usr/share/doc/flamerobin/html -> ../../flamerobin/docs
  /usr/share/doc/flamerobin/html/html.css (flamerobin) != 
/usr/share/flamerobin/docs/html.css (?)
/usr/share/doc/flamerobin/html -> ../../flamerobin/docs


cheers,

Andreas

Bug#985288: chai: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

[Andreas Beckmann]

Package: chai
Version: 4.2.0+ds+~4.2.14-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.

This was observed on the following upgrade paths:

  buster -> bullseye

For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#copyright-information

For other overwritten locations anything interesting may happen.

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#details-of-unpack-phase-of-installation-or-upgrade

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


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

0m40.7s ERROR: FAIL: silently overwrites files via directory symlinks:
  /usr/share/doc/chai/History.md.gz (chai) != 
/usr/share/doc/libjs-chai/History.md.gz (libjs-chai)
/usr/share/doc/chai -> libjs-chai
  /usr/share/doc/chai/changelog.Debian.gz (chai) != 
/usr/share/doc/libjs-chai/changelog.Debian.gz (libjs-chai)
/usr/share/doc/chai -> libjs-chai
  /usr/share/doc/chai/changelog.gz (chai) != 
/usr/share/doc/libjs-chai/changelog.gz (libjs-chai)
/usr/share/doc/chai -> libjs-chai
  /usr/share/doc/chai/copyright (chai) != /usr/share/doc/libjs-chai/copyright 
(libjs-chai)
/usr/share/doc/chai -> libjs-chai


cheers,

Andreas


chai_4.2.0+ds+~4.2.14-3.log.gz
Description: application/gzip

Bug#985287: nagvis: unhandled symlink to directory conversion: /usr/share/nagvis/share/server/core/ext/php-gettext-1.0.12 -> ../../../../../php/php-php-gettext

[Andreas Beckmann]

Package: nagvis
Version: 1:1.9.25-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.

This was observed on the following upgrade paths:

  buster -> bullseye

For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#copyright-information

For other overwritten locations anything interesting may happen.

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#details-of-unpack-phase-of-installation-or-upgrade

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


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

2m15.1s ERROR: FAIL: silently overwrites files via directory symlinks:
  /usr/share/nagvis/share/server/core/ext/php-gettext-1.0.12/AUTHORS (nagvis) 
!= /usr/share/php/php-php-gettext/AUTHORS (?)
/usr/share/nagvis/share/server/core/ext/php-gettext-1.0.12 -> 
../../../../../php/php-php-gettext
  /usr/share/nagvis/share/server/core/ext/php-gettext-1.0.12/COPYING (nagvis) 
!= /usr/share/php/php-php-gettext/COPYING (?)
/usr/share/nagvis/share/server/core/ext/php-gettext-1.0.12 -> 
../../../../../php/php-php-gettext
  /usr/share/nagvis/share/server/core/ext/php-gettext-1.0.12/README (nagvis) != 
/usr/share/php/php-php-gettext/README (?)
/usr/share/nagvis/share/server/core/ext/php-gettext-1.0.12 -> 
../../../../../php/php-php-gettext
  /usr/share/nagvis/share/server/core/ext/php-gettext-1.0.12/gettext.inc 
(nagvis) != /usr/share/php/php-php-gettext/gettext.inc (php-php-gettext)
/usr/share/nagvis/share/server/core/ext/php-gettext-1.0.12 -> 
../../../../../php/php-php-gettext
  /usr/share/nagvis/share/server/core/ext/php-gettext-1.0.12/gettext.php 
(nagvis) != /usr/share/php/php-php-gettext/gettext.php (php-php-gettext)
/usr/share/nagvis/share/server/core/ext/php-gettext-1.0.12 -> 
../../../../../php/php-php-gettext
  /usr/share/nagvis/share/server/core/ext/php-gettext-1.0.12/streams.php 
(nagvis) != /usr/share/php/php-php-gettext/streams.php (php-php-gettext)
/usr/share/nagvis/share/server/core/ext/php-gettext-1.0.12 -> 
../../../../../php/php-php-gettext


cheers,

Andreas


nagvis_1:1.9.25-1.log.gz
Description: application/gzip

Bug#985286: libbatteries-ocaml-doc: unhandled symlink to directory conversion: /usr/share/doc/libbatteries-ocaml-dev/examples -> ../libbatteries-ocaml-doc/examples

[Andreas Beckmann]

Package: libbatteries-ocaml-doc
Version: 3.1.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.

This was observed on the following upgrade paths:

  buster -> bullseye

For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#copyright-information

For other overwritten locations anything interesting may happen.

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#details-of-unpack-phase-of-installation-or-upgrade

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


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

0m38.7s ERROR: installs objects over existing directory symlinks:
  /usr/share/doc/libbatteries-ocaml-dev/examples/battop.ml 
(libbatteries-ocaml-doc) != 
/usr/share/doc/libbatteries-ocaml-doc/examples/battop.ml (?)
/usr/share/doc/libbatteries-ocaml-dev/examples -> 
../libbatteries-ocaml-doc/examples


cheers,

Andreas


libbatteries-ocaml-doc_3.1.0-1.log.gz
Description: application/gzip

Bug#985284: hyphy-common: unhandled symlink to directory conversion: /usr/lib/hyphy -> ../share/hyphy

[Andreas Beckmann]

Package: hyphy-common
Version: 2.5.28+dfsg-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.

This was observed on the following upgrade paths:

  buster -> bullseye

For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#copyright-information

For other overwritten locations anything interesting may happen.

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#details-of-unpack-phase-of-installation-or-upgrade

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


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

0m33.7s ERROR: installs objects over existing directory symlinks:
  /usr/lib/hyphy/bin (hyphy-common) != /usr/share/hyphy/bin (?)
/usr/lib/hyphy -> ../share/hyphy
  /usr/lib/hyphy/bin/simd-dispatch (hyphy-common) != 
/usr/share/hyphy/bin/simd-dispatch (?)
/usr/lib/hyphy -> ../share/hyphy


cheers,

Andreas


hyphy-common_2.5.28+dfsg-2.log.gz
Description: application/gzip

Bug#985282: dnsmasq: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

[Andreas Beckmann]

Package: dnsmasq
Version: 2.84-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.

This was observed on the following upgrade paths:

  buster -> bullseye

For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#copyright-information

For other overwritten locations anything interesting may happen.

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#details-of-unpack-phase-of-installation-or-upgrade

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


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

0m36.5s ERROR: FAIL: silently overwrites files via directory symlinks:
  /usr/share/doc/dnsmasq/changelog.Debian.gz (dnsmasq) != 
/usr/share/doc/dnsmasq-base/changelog.Debian.gz (dnsmasq-base)
/usr/share/doc/dnsmasq -> dnsmasq-base
  /usr/share/doc/dnsmasq/copyright (dnsmasq) != 
/usr/share/doc/dnsmasq-base/copyright (dnsmasq-base)
/usr/share/doc/dnsmasq -> dnsmasq-base


cheers,

Andreas


dnsmasq_2.84-1.log.gz
Description: application/gzip

Bug#985281: r-cran-dt: unhandled symlink to directory conversion: /usr/lib/R/site-library/DT/htmlwidgets/lib/datatables-extensions -> ../../../../../../share/javascript/jquery-datatables-extensions

[Andreas Beckmann]

Package: r-cran-dt
Version: 0.17+dfsg-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.

This was observed on the following upgrade paths:

  buster -> bullseye

For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#copyright-information

For other overwritten locations anything interesting may happen.

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#details-of-unpack-phase-of-installation-or-upgrade

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


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

1m34.8s ERROR: FAIL: silently overwrites files via directory symlinks:
  /usr/lib/R/site-library/DT/htmlwidgets/lib/datatables-extensions/AutoFill 
(r-cran-dt) != /usr/share/javascript/jquery-datatables-extensions/AutoFill 
(libjs-jquery-datatables-extensions)
/usr/lib/R/site-library/DT/htmlwidgets/lib/datatables-extensions -> 
../../../../../../share/javascript/jquery-datatables-extensions
  /usr/lib/R/site-library/DT/htmlwidgets/lib/datatables-extensions/Buttons 
(r-cran-dt) != /usr/share/javascript/jquery-datatables-extensions/Buttons 
(libjs-jquery-datatables-extensions)
/usr/lib/R/site-library/DT/htmlwidgets/lib/datatables-extensions -> 
../../../../../../share/javascript/jquery-datatables-extensions
  /usr/lib/R/site-library/DT/htmlwidgets/lib/datatables-extensions/Buttons/css 
(r-cran-dt) != /usr/share/javascript/jquery-datatables-extensions/Buttons/css 
(libjs-jquery-datatables-extensions)
/usr/lib/R/site-library/DT/htmlwidgets/lib/datatables-extensions -> 
../../../../../../share/javascript/jquery-datatables-extensions
[...]
  /usr/lib/R/site-library/DT/htmlwidgets/lib/datatables/images (r-cran-dt) != 
/usr/share/javascript/jquery-datatables/images (libjs-jquery-datatables)
/usr/lib/R/site-library/DT/htmlwidgets/lib/datatables -> 
../../../../../../share/javascript/jquery-datatables
  /usr/lib/R/site-library/DT/htmlwidgets/lib/datatables/js (r-cran-dt) != 
/usr/share/javascript/jquery-datatables/js (?)
/usr/lib/R/site-library/DT/htmlwidgets/lib/datatables -> 
../../../../../../share/javascript/jquery-datatables


cheers,

Andreas

Processed: your mail

[Debian Bug Tracking System]

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

> unarchive 845960
Bug #845960 {Done: Debian FTP Masters } 
[src:x-tile] x-tile: depends on python-gnome2 which deprecated
Unarchived Bug 845960
> reopen 845960 =
Bug #845960 {Done: Debian FTP Masters } 
[src:x-tile] x-tile: depends on python-gnome2 which deprecated
'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 2.5-3+rm.
> --
Stopping processing here.

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

Bug#985043: nagios4-cgi: fails to install with --install-recommends enabled

[Russell Stuart]

I can't reproduce this.

I've tried running piuparts on the .changes file, I've manually 
installed it into a minimal chroot, and in fact I use it in production. 
 I used piuparts on bullseye, amd64.


Attached is the output of my run "piuparts --apt 
--logfile=/tmp/nagios4-cgi_4.46-2.log nagios4-cgi".  It passed, of course.


If you can give me a clue on how to reproduce it, I'd appreciate it.  I 
can't find a way to reproduce it in a few days, I'll reduce the severity.


nagios4-cgi_4.46-2.log.gz
Description: application/gzip

Bug#985269: libint1: ships broken library symlinks: /usr/lib/lib*-stable.so.1 -> lib*.so.1

[Andreas Beckmann]

On 15/03/2021 11.24, Michael Banck wrote:

I guess dh_link can't cope with multiarch, so we will have to to the
symlinking in an install override, will look into it.


In debhelper-compat 13 it could, but now is not the time to switch.

Andreas

Bug#982699: marked as done (intake: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13)

[Debian Bug Tracking System]

Your message dated Mon, 15 Mar 2021 10:50:45 +
with message-id 
and subject line Bug#982699: fixed in intake 0.6.1-1
has caused the Debian Bug report #982699,
regarding intake: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i 
python{version} -p 3.9 returned exit code 13
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.)


-- 
982699: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982699
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: intake
Version: 0.6.0-4
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210213 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_install
> # For some reason, not all data is movable via install or dh_install, so
> # just force copy (and overwrite if needed) for pytest to actually work
> for py in `py3versions -sv` ; do cp -a intake/source/tests 
> .pybuild/cpython3_${py}_intake/build/intake/source; done
> PYBUILD_SYSTEM=custom \
>  PYBUILD_TEST_ARGS='cd {build_dir}; 
> PATH=/<>/debian/{package}/usr/bin:/<>/debian/{package}/usr/lib:/<>/debian/{package}/build/intake:$PATH
>  {interpreter} -m pytest' \
>  dh_auto_test --buildsystem=pybuild
> I: pybuild base:232: cd /<>/.pybuild/cpython3_3.9_intake/build; 
> PATH=/<>/debian/python3-intake/usr/bin:/<>/debian/python3-intake/usr/lib:/<>/debian/python3-intake/build/intake:$PATH
>  python3.9 -m pytest
> = test session starts 
> ==
> platform linux -- Python 3.9.1+, pytest-6.0.2, py-1.10.0, pluggy-0.13.0
> rootdir: /<>
> collected 371 items / 9 skipped / 362 selected
> 
> intake/auth/tests/test_auth.py ..[  
> 1%]
> intake/catalog/tests/test_alias.py ..[  
> 2%]
> intake/catalog/tests/test_auth_integration.py .. [  
> 2%]
> intake/catalog/tests/test_caching_integration.py ..  [  
> 7%]
> intake/catalog/tests/test_core.py .  [  
> 7%]
> intake/catalog/tests/test_default.py .   [  
> 8%]
> intake/catalog/tests/test_discovery.py . [  
> 8%]
> intake/catalog/tests/test_gui.py ..s..s  [  
> 9%]
> intake/catalog/tests/test_local.py . [ 
> 19%]
> .[ 
> 33%]
> intake/catalog/tests/test_parameters.py  [ 
> 36%]
> intake/catalog/tests/test_persist.py .s  [ 
> 36%]
> intake/catalog/tests/test_reload_integration.py  [ 
> 38%]
> intake/catalog/tests/test_remote_integration.py  [ 
> 44%]
> ...  [ 
> 45%]
> intake/catalog/tests/test_utils.py ...   [ 
> 47%]
> intake/catalog/tests/test_zarr.py ...[ 
> 47%]
> intake/cli/client/tests/test_cache.py .. [ 
> 49%]
> intake/cli/client/tests/test_conf.py .   [ 
> 50%]
> intake/cli/client/tests/test_local_integration.py .  [ 
> 53%]
> intake/cli/server/tests/test_serializer.py sss.  [ 
> 56%]
> intake/cli/server/tests/test_server.py ..ss..[ 
> 59%]
> intake/cli/tests/test_util.py    [ 
> 61%]
> intake/container/tests/test_generics.py .[ 
> 61%]
> intake/container/tests/test_persist.py ...s  [ 
> 62%]
> intake/gui/tests/test_init_gui.py ..s[ 
> 63%]
> intake/source/tests/test_base.py .   [ 
> 68%]
> intake/source/tests/test_cache.py ...s   [ 
> 72%]
> intake/source/tests/test_csv.py ..FFF..s..   [ 
> 76%]
> intake/source/tests/test_discovery.py .. [ 
> 77%]
> intake/source/tests/test_npy.py ...  [ 
> 80%]
> intake/source/tests/test_text.py ..  [ 
> 85%]
> intake/source/tests/test_utils.py ...[ 
> 94%]
> intake/tests/test_config.py   

Bug#984984: marked as done (hwloc-contrib: FTBFS with latest nvidia-alternative)

[Debian Bug Tracking System]

Your message dated Mon, 15 Mar 2021 10:37:56 +
with message-id 
and subject line Bug#984984: fixed in hwloc-contrib 2.4.1+dfsg-2
has caused the Debian Bug report #984984,
regarding hwloc-contrib: FTBFS with latest nvidia-alternative
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.)


-- 
984984: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984984
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hwloc-contrib
Version: 2.4.1+dfsg-1
Severity: serious
Justification: FTBFS

With the new nvidia-alternative package which fixed shipping
libnvidia-ml.so (see #984881), hwloc-contrib now FTBFS:

   dh_missing -a
dh_missing: warning: usr/lib/x86_64-linux-gnu/hwloc/hwloc_nvml.so exists in 
debian/tmp but is not installed to anywhere

That's because hwloc can now build its nvml plugin. It happens that we'd
want to ship indeed, so I'll propose to use the attached patch.

Samuel

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-proposed-updates-debug'), (500, 'testing-proposed-updates'), (500, 
'testing-debug'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), (500, 
'proposed-updates'), (500, 'oldoldstable'), (500, 'buildd-unstable'), (500, 
'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental-debug'), 
(1, 'buildd-experimental'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.11.0 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
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
diff --git a/debian/libhwloc-contrib-plugins.install 
b/debian/libhwloc-contrib-plugins.install
index 59555c70..80553c88 100644
--- a/debian/libhwloc-contrib-plugins.install
+++ b/debian/libhwloc-contrib-plugins.install
@@ -1 +1,2 @@
 usr/lib/*/hwloc/hwloc_cuda.so
+usr/lib/*/hwloc/hwloc_nvml.so
--- End Message ---
--- Begin Message ---
Source: hwloc-contrib
Source-Version: 2.4.1+dfsg-2
Done: Samuel Thibault 

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

Debian distribution maintenance software
pp.
Samuel Thibault  (supplier of updated hwloc-contrib 
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: Thu, 11 Mar 2021 16:01:54 +0100
Binary: libhwloc-contrib-plugins libhwloc-contrib-plugins-dbgsym
Source: hwloc-contrib
Architecture: amd64 arm64 ppc64el source
Version: 2.4.1+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Samuel Thibault 
Changed-By: Samuel Thibault 
Closes: 984984
Description: 
 libhwloc-contrib-plugins - Hierarchical view of the machine - contrib plugins
Changes:
 hwloc-contrib (2.4.1+dfsg-2) unstable; urgency=medium
 .
   * libhwloc-contrib-plugins.install: Install the nvml plugin again
 (Closes: Bug#984984)
Checksums-Sha1: 
 d6877fdf1def8943d5d3d7e7880ff70bab160088 2398 hwloc-contrib_2.4.1+dfsg-2.dsc
 d3612a04682d0adb5a1fb7a4f697bde9c14f2095 12244 
hwloc-contrib_2.4.1+dfsg-2.debian.tar.xz
 0356f64891f753b944f7b9a1e47afcb641d017f3 11007 
hwloc-contrib_2.4.1+dfsg-2_amd64.buildinfo
 f9d4b2e1316a6a299d0a05537f4bb1e2723d959f 18792 
libhwloc-contrib-plugins-dbgsym_2.4.1+dfsg-2_amd64.deb
 7a6bfe95b3d21b5d3c8d8169f61d4991c1f3befe 14468 
libhwloc-contrib-plugins_2.4.1+dfsg-2_amd64.deb
 2e0fdb6db503703d226f80b5df0586cfdec228b8 9623 
hwloc-contrib_2.4.1+dfsg-2_arm64.buildinfo
 f9e4d3faafd160cd206794c55cc0c11987b2dad0 18996 
libhwloc-contrib-plugins-dbgsym_2.4.1+dfsg-2_arm64.deb
 2e81dbacb60c5aa232cfcf21c20159cef37860c4 14568 
libhwloc-contrib-plugins_2.4.1+dfsg-2_arm64.deb
 764cf685cba92ffe0b7eb1ad6c774fa0cbf44178 9811 
hwloc-contrib_2.4.1+dfsg-2_ppc64el.buildinfo
 641da555f2a9f33367db84eccb6f8a31d421b782 19240 
libhwloc-contrib-plugins-dbgsym_2.4.1+dfsg-2_ppc64el.deb
 5e2a373c66c3826e5cba2290811bcc791d3a6dff 15448 
libhwloc-contrib-plugins_2.4.1+dfsg-2_ppc64el.deb
Checksums-Sha256: 

Processed: tagging 985040

[Debian Bug Tracking System]

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

> tags 985040 + pending
Bug #985040 [qemu-system-data] qemu-system-data: too tight dependencies 
breaking on binNMUs
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#985269: [Debichem-devel] Bug#985269: libint1: ships broken library symlinks: /usr/lib/lib*-stable.so.1 -> lib*.so.1

[Michael Banck]

Hi,

On Mon, Mar 15, 2021 at 10:40:09AM +0100, Andreas Beckmann wrote:
> during a test with piuparts I noticed your package ships (or creates)
> a broken symlink.

Thanks for the report.
 
> From the attached log (scroll to the bottom...):
> 
>   libint1: MISSING OBJECT /usr/lib/libderiv-stable.so.1
>   libint1: MISSING OBJECT /usr/lib/libint-stable.so.1
>   libint1: MISSING OBJECT /usr/lib/libr12-stable.so.1

Those are legacy symlinks. I am not sure they are still needed, but
probably now isn't the time to remove them either.
 
> The dangling symlinks get "cleaned up" by ldconfig.
> 
> The package ships the following libraries and symlinks:
> 
> -rw-r--r-- root/root  20421064 2021-03-04 15:25 
> ./usr/lib/x86_64-linux-gnu/libderiv.so.1.0.0
> -rw-r--r-- root/root   9215552 2021-03-04 15:25 
> ./usr/lib/x86_64-linux-gnu/libint.so.1.0.0
> -rw-r--r-- root/root   9816208 2021-03-04 15:25 
> ./usr/lib/x86_64-linux-gnu/libr12.so.1.0.0
> lrwxrwxrwx root/root 0 2021-03-04 15:25 
> ./usr/lib/libderiv-stable.so.1 -> libderiv.so.1
> lrwxrwxrwx root/root 0 2021-03-04 15:25 ./usr/lib/libint-stable.so.1 
> -> libint.so.1
> lrwxrwxrwx root/root 0 2021-03-04 15:25 ./usr/lib/libr12-stable.so.1 
> -> libr12.so.1
> lrwxrwxrwx root/root 0 2021-03-04 15:25 
> ./usr/lib/x86_64-linux-gnu/libderiv.so.1 -> libderiv.so.1.0.0
> lrwxrwxrwx root/root 0 2021-03-04 15:25 
> ./usr/lib/x86_64-linux-gnu/libint.so.1 -> libint.so.1.0.0
> lrwxrwxrwx root/root 0 2021-03-04 15:25 
> ./usr/lib/x86_64-linux-gnu/libr12.so.1 -> libr12.so.1.0.0
> 
> Do you need to move the lib*-stable.so.1 symlinks to 
> /usr/lib/${DEB_HOST_MULTIARCH} ?

I guess dh_link can't cope with multiarch, so we will have to to the
symlinking in an install override, will look into it.


Michael

Bug#981066: aerc: Cannot Render HTML Emails After Latest w3m Update in bullseye

[Tatsuya Kinoshita]

Control: retitle -1 aerc: cannot display either plaintext or HTML emails
Control: tags -1 + patch

On 2021-01-26 at 07:50 +1030, Solya. Reka wrote:
> After I did a apt upgrade today (which upgraded w3m from 0.5.3+git20210102-1 
> to 
> 0.5.3+git20210102-2), I am no longer able to display either plaintext or HTML 
> emails. The message viewer simply display a empty screen instead of email 
> content.

It seems not relate to w3m.  On my sid amd64 environment, with the
fresh installed aerc 0.3.0-2+b2, all the contents of the emails are
empty even if text/html filter is disabled (by default) in
~/.config/aerc/aerc.conf.  Even `:pipe less` and `:pipe cat` fail.

I've skimmed throw the upstream git log, and found the related commit.

See the attached patch against aerc 0.3.0-2.

Thanks,
-- 
Tatsuya Kinoshita
commit ce90d8fb9beabe991e27740c464f95ac86d74b20
Author: Tatsuya Kinoshita 
Date:   Mon Mar 15 19:07:39 2021 +0900

New patch fix-empty-content.patch to display email body (Closes: #981066)

diff --git a/debian/patches/fix-empty-content.patch b/debian/patches/fix-empty-content.patch
new file mode 100644
index 000..65412d6
--- /dev/null
+++ b/debian/patches/fix-empty-content.patch
@@ -0,0 +1,29 @@
+Subject: Use stdout as controlling terminal
+Origin: backport, https://git.sr.ht/~sircmpwn/aerc/commit/dc281e46d2aceaab6a7b7a290f9af89fef46159d
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983165
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981066
+
+Soves an issue with go1.15 not letting ctty be a parent. See
+https://github.com/creack/pty/pull/97 for more details.
+
+diff --git a/widgets/terminal.go b/widgets/terminal.go
+index 8fc38ce..77da71e 100644
+--- a/widgets/terminal.go
 b/widgets/terminal.go
+@@ -4,6 +4,7 @@ import (
+ 	"os"
+ 	"os/exec"
+ 	"sync"
++	"syscall"
+ 
+ 	"git.sr.ht/~sircmpwn/aerc/lib/ui"
+ 
+@@ -237,7 +238,7 @@ func (term *Terminal) Draw(ctx *ui.Context) {
+ 
+ 		if term.pty == nil {
+ 			term.vterm.SetSize(ctx.Height(), ctx.Width())
+-			tty, err := pty.StartWithSize(term.cmd, &winsize)
++			tty, err := pty.StartWithAttrs(term.cmd, &winsize, &syscall.SysProcAttr{Setsid: true, Setctty: true, Ctty: 1})
+ 			term.pty = tty
+ 			if err != nil {
+ term.Close(err)
diff --git a/debian/patches/series b/debian/patches/series
index 3b5d2bb..6e8232a 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -2,3 +2,4 @@ use-creack-pty.diff
 fix-go-maildir-usage.diff
 temp-disable-beep.diff
 fix-installation-directories.diff
+fix-empty-content.patch


pgpb5ctzaJDwJ.pgp
Description: PGP signature

Processed: Re: aerc: Cannot Render HTML Emails After Latest w3m Update in bullseye

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 aerc: cannot display either plaintext or HTML emails
Bug #981066 [aerc] aerc: Cannot Render HTML Emails After Latest w3m Update in 
bullseye
Bug #983165 [aerc] aerc: Does not display content of the emails
Changed Bug title to 'aerc: cannot display either plaintext or HTML emails' 
from 'aerc: Cannot Render HTML Emails After Latest w3m Update in bullseye'.
Changed Bug title to 'aerc: cannot display either plaintext or HTML emails' 
from 'aerc: Does not display content of the emails'.
> tags -1 + patch
Bug #981066 [aerc] aerc: cannot display either plaintext or HTML emails
Bug #983165 [aerc] aerc: cannot display either plaintext or HTML emails
Added tag(s) patch.
Added tag(s) patch.

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

Bug#985273: libebitdo-dev: uninstallable in stretch

[Andreas Beckmann]

Package: libebitdo-dev
Version: 0.7.4-2+deb9u1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: close -1

Hi,

during a test with piuparts I noticed your package is no longer
installable in stretch.

libebitdo-dev 0.7.4-2+deb9u1 is a cruft package still available in
stetch/updates, but it is no longer built by src:fwupd 0.8.3-1 in
stretch.

  The following packages have unmet dependencies:
   libebitdo-dev : Depends: libdfu1 (= 0.7.4-2+deb9u1) but 0.8.3-1 is to be 
installed


Cheers,

Andreas

Processed: libebitdo-dev: uninstallable in stretch

[Debian Bug Tracking System]

Processing control commands:

> close -1
Bug #985273 [libebitdo-dev] libebitdo-dev: uninstallable in stretch
Warning: Unknown package 'libebitdo-dev'
Marked Bug as done
Warning: Unknown package 'libebitdo-dev'

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

Processed: retitle 928422 to rust-doc: unsatisfiable Depends: fonts-open-sans in jessie, stretch, tagging 928422 ...

[Debian Bug Tracking System]

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

> retitle 928422 rust-doc: unsatisfiable Depends: fonts-open-sans in jessie, 
> stretch
Bug #928422 [rust-doc] rust-doc: unsatisfiable Depends: fonts-open-sans in 
jessie
Changed Bug title to 'rust-doc: unsatisfiable Depends: fonts-open-sans in 
jessie, stretch' from 'rust-doc: unsatisfiable Depends: fonts-open-sans in 
jessie'.
> tags 928422 + stretch
Bug #928422 [rust-doc] rust-doc: unsatisfiable Depends: fonts-open-sans in 
jessie, stretch
Added tag(s) stretch.
> found 928422 1.34.2+dfsg1-1~deb9u1
Bug #928422 [rust-doc] rust-doc: unsatisfiable Depends: fonts-open-sans in 
jessie, stretch
Marked as found in versions rustc/1.34.2+dfsg1-1~deb9u1.
> thanks
Stopping processing here.

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

Processed: user debian...@lists.debian.org, usertagging 942889 ..., found 984931 in 1:2.31.0~rc2+next.20210309-1 ...

[Debian Bug Tracking System]

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

> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
> usertags 942889 piuparts
There were no usertags set.
Usertags are now: piuparts.
> found 942889 1:0.9.24~git20190922-f7d30d-1~exp3
Bug #942889 [src:tuxpaint] tuxpaint: FTBFS on several architectures in 
experimental
Marked as found in versions tuxpaint/1:0.9.24~git20190922-f7d30d-1~exp3.
> found 984931 1:2.31.0~rc2+next.20210309-1
Bug #984931 [git-el,elpa-magit] git-el,elpa-magit: fails to install: 
/usr/lib/emacsen-common/packages/install/git emacs failed at 
/usr/lib/emacsen-common/lib.pl line 19,  line 7.
There is no source info for the package 'elpa-magit' at version 
'1:2.31.0~rc2+next.20210309-1' with architecture ''
Marked as found in versions git/1:2.31.0~rc2+next.20210309-1.
> usertags 984622 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 984622 + librust-derive-more+generate-parsing-rs-dev
Bug #984622 [src:rust-derive-more] rust-derive-more uninstallable, unmigratable 
due to missing rust-peg
Added indication that 984622 affects librust-derive-more+generate-parsing-rs-dev
> thanks
Stopping processing here.

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

Bug#985269: libint1: ships broken library symlinks: /usr/lib/lib*-stable.so.1 -> lib*.so.1

[Andreas Beckmann]

Package: libint1
Version: 1.2.1-5
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

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

  libint1: MISSING OBJECT /usr/lib/libderiv-stable.so.1
  libint1: MISSING OBJECT /usr/lib/libint-stable.so.1
  libint1: MISSING OBJECT /usr/lib/libr12-stable.so.1

The dangling symlinks get "cleaned up" by ldconfig.

The package ships the following libraries and symlinks:

-rw-r--r-- root/root  20421064 2021-03-04 15:25 
./usr/lib/x86_64-linux-gnu/libderiv.so.1.0.0
-rw-r--r-- root/root   9215552 2021-03-04 15:25 
./usr/lib/x86_64-linux-gnu/libint.so.1.0.0
-rw-r--r-- root/root   9816208 2021-03-04 15:25 
./usr/lib/x86_64-linux-gnu/libr12.so.1.0.0
lrwxrwxrwx root/root 0 2021-03-04 15:25 ./usr/lib/libderiv-stable.so.1 
-> libderiv.so.1
lrwxrwxrwx root/root 0 2021-03-04 15:25 ./usr/lib/libint-stable.so.1 -> 
libint.so.1
lrwxrwxrwx root/root 0 2021-03-04 15:25 ./usr/lib/libr12-stable.so.1 -> 
libr12.so.1
lrwxrwxrwx root/root 0 2021-03-04 15:25 
./usr/lib/x86_64-linux-gnu/libderiv.so.1 -> libderiv.so.1.0.0
lrwxrwxrwx root/root 0 2021-03-04 15:25 
./usr/lib/x86_64-linux-gnu/libint.so.1 -> libint.so.1.0.0
lrwxrwxrwx root/root 0 2021-03-04 15:25 
./usr/lib/x86_64-linux-gnu/libr12.so.1 -> libr12.so.1.0.0

Do you need to move the lib*-stable.so.1 symlinks to 
/usr/lib/${DEB_HOST_MULTIARCH} ?


cheers,

Andreas


libint1_1.2.1-5.log.gz
Description: application/gzip

Bug#985253: mount.s3ql: ERROR: Uncaught top-level exception, AttributeError: lowlevel

[bgr001]

Package: s3ql
Version: 3.7.0+dfsg-2
Severity: grave
Tags: upstream
Justification: renders package unusable
X-Debbugs-Cc: bgr...@mailbox.org

Dear Maintainer,

# mount.s3ql local:///root/sdb_s3ql/ /root/x
Using 10 upload threads.
Autodetected 1048514 file descriptors available for cache entries
Using cached metadata.
Setting cache size to 132879 MB
Loaded 0 entries from cache
ERROR: Uncaught top-level exception:
Traceback (most recent call last):
  File "/usr/bin/mount.s3ql", line 33, in 
sys.exit(load_entry_point('s3ql==3.7.0', 'console_scripts',
'mount.s3ql')())
  File "/usr/lib/s3ql/s3ql/mount.py", line 131, in main
trio.run(main_async, options, stdout_log_handler)
  File "/usr/lib/python3/dist-packages/trio/_core/_run.py", line 1804, in run
raise runner.main_task_outcome.error
  File "/usr/lib/s3ql/s3ql/mount.py", line 207, in main_async
block_cache.init(options.threads)
  File "/usr/lib/s3ql/s3ql/block_cache.py", line 222, in init
self.trio_token = trio.lowlevel.current_trio_token()
  File "/usr/lib/python3/dist-packages/trio/_deprecate.py", line 125, in
__getattr__
raise AttributeError(name)
AttributeError: lowlevel


-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-4-amd64 (SMP w/12 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages s3ql depends on:
ii  fuse3 [fuse]  3.10.2-2
ii  libc6 2.31-9
ii  libjs-sphinxdoc   3.4.3-1
ii  libsqlite3-0  3.34.1-3
ii  procps2:3.3.17-4
ii  psmisc23.4-2
ii  python3   3.9.2-2
ii  python3-apsw  3.34.0-r1-1
ii  python3-cryptography  3.3.2-1
ii  python3-defusedxml0.6.0-2
ii  python3-dugong3.8.1+dfsg-1
ii  python3-google-auth   1.5.1-3
ii  python3-google-auth-oauthlib  0.4.2-1
ii  python3-pkg-resources 52.0.0-3
ii  python3-pyfuse3   3.2.0-2
ii  python3-requests  2.25.1+dfsg-2
ii  python3-systemd   234-3+b4
ii  python3-trio  0.13.0-2

s3ql recommends no packages.

s3ql suggests no packages.

Bug#985265: psgml: modifies shipped files: /usr/share/emacs/site-lisp/psgml/psgml-init.el

[Andreas Beckmann]

Package: psgml
Version: 1.4.0-10
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package modifies files it has 
shipped.

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

1m16.0s ERROR: FAIL: debsums reports modifications inside the chroot:
  /usr/share/emacs/site-lisp/psgml/psgml-init.el

The modified version of the file is actually an empty file.

This seems to be limited to tests with --install-recommends enabled or upgrades
from buster.

/usr/lib/emacsen-common/packages/install/psgml contains the following code
which is the likely culprit.

sed -e "s|=F|/usr/share/$FLAVOUR/site-lisp/$PACKAGE|" \
$STARTFILE > $ELDIR/$STARTFILE

I do not know anything about emacs packaging, no idea what would be correct.


cheers,

Andreas


psgml_1.4.0-10.log.gz
Description: application/gzip

Bug#985264: librust-html2text-dev: depends on unavailable librust-clippy-0.0.302+default-dev

[Andreas Beckmann]

Package: librust-html2text-dev
Version: 0.2.1-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package is not
installable in sid:

  The following packages have unmet dependencies:
   librust-html2text-dev : Depends: librust-clippy-0.0.302+default-dev but it 
is not installable


Cheers,

Andreas

Bug#985033: debian/copyright is not up-to-date: coderay seems to have been relicensed under MIT license

[Vivek K J]

On Fri, 12 Mar 2021 01:30:19 +0100 Daniel Leidert  wrote:
> Source: coderay
> Version: 1.1.3-3
> Severity: serious
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> It seem the coderay sources are now licensed under the MIT license and not
> under the LGPL license. debian/copyright seems to be outdated and wrong here.
> 
> Regards, Daniel
> 
> 
> - -- System Information:
> Debian Release: bullseye/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
> 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 5.10.0-4-amd64 (SMP w/8 CPU threads)
> Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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
> 
> - -- no debconf information
> 
> -BEGIN PGP SIGNATURE-
> 
> iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAmBKthsACgkQS80FZ8KW
> 0F387w//ezc1er6Hv8c7swmmwgK8XfokzAcxFbktXyIsUOwN+s2fKlFwjinFkArU
> PP8lOe7qzB2vB5eol19vofYdDzJoOqo/RCzsS+Q8Rm3gUzcyTF2pIeubzlNqZMf2
> KMYaERHnfrGlLklcOzt+x8JfRvmxS2MAFHNLBuws0k9yISdWfW36DeCFiz0Miqik
> VrPAaWMRFUzaqnH3lXEoi342OomkDq2wmx7YnqRd4ESHTWdpAY5b9dC8r6tCnynj
> zcspt/0uPnXBKKPuBKXsucBoLr80te+x/7DZ/iLILAbIdEZ+o1jzCu3pCRXQUFdK
> vNOnwaBVhDl9aciXTrj1ocbNS1shximlu6vJMaMTB5MXVNt5ph691jazr6bYXjn2
> MZU8EK5fkPnYIkX3DOGGZMjuQ5wMN55Z3Udgf+pUE9oXDprc+0vxuLmq6UtLrHKy
> uQm/WOd3Fj+r71s5zaRqlf7gShQU2oV23/4PLWC84nswoGkZTnk9yj5X4tw+HdfS
> 82+iOGayRny2a+EkglGT4IvOvXSdPnXnucjronzpf6s5kw/JP9BRyyF85AWM87q2
> 6zjycLQo+j3xh3CV4jgNC9pRC6yUTj5YsxnYPIM7v0YWgQBwEzAz6JLBMU/2zEvO
> JRHm+XskHA+U6PsV4ccyA4m7zEKPsV10xRrqrZhQekf96BvaQ8Y=
> =GfoC
> -END PGP SIGNATURE-
> 
> 
Submitted a merge request[1] which closes this bug.

[1] - https://salsa.debian.org/ruby-team/coderay/-/merge_requests/1
-- 
Greetings,

Vivek K J
vive...@tchncs.de
www.vivekkj.me

Bug#985263: librust-num-bigint+quickcheck-macros-dev: depends on unavailable librust-quickcheck-macros-0.8-dev

[Andreas Beckmann]

Package: librust-num-bigint+quickcheck-macros-dev
Version: 0.2.6-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package is not
installable in sid:

  The following packages have unmet dependencies:
   librust-num-bigint+quickcheck-macros-dev : Depends: 
librust-quickcheck-macros-0.8-dev but it is not installable


Cheers,

Andreas

Bug#985262: librust-migrations-internals+barrel-dev: depends on unavailabe librust-barrel+default-dev

[Andreas Beckmann]

Package: librust-migrations-internals+barrel-dev
Version: 1.4.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package is not
installable in sid:

  The following packages have unmet dependencies:
   librust-migrations-internals+barrel-dev : Depends: 
librust-barrel+default-dev (< 0.2.1-~~)
 Depends: 
librust-barrel+diesel-filled-dev (< 0.2.1-~~) but it is not installable


Cheers,

Andreas

Bug#985190: marked as done (xsane: /usr/share/sane/xsane/xsane-startimage.pnm missing after buster->bulleye upgrade)

[Debian Bug Tracking System]

Your message dated Mon, 15 Mar 2021 07:09:39 +
with message-id 
and subject line Bug#985190: fixed in xsane 0.999-10
has caused the Debian Bug report #985190,
regarding xsane: /usr/share/sane/xsane/xsane-startimage.pnm missing after 
buster->bulleye upgrade
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.)


-- 
985190: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985190
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xsane
Version: 0.999-9
Severity: serious
Tags: patch
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'buster'.
It installed fine in 'buster', then the upgrade to 'bullseye' fails.

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

1m56.7s ERROR: FAIL: debsums reports modifications inside the chroot:
  debsums: missing file /usr/share/sane/xsane/xsane-startimage.pnm (from xsane 
package)

/usr/share/sane/xsane/xsane-startimage.pnm moved from
xsane-common 0.999-6 (buster) to xsane 0.999-9 (bullseye) without
adding corresponding Breaks+Replaces. 
Contrarily, there is an ancient unversioned Replaces: xsane in
xsane-commmon which now starts to cause havoc.

The attached patch fixes the upgrade path.

cheers,

Andreas
>From 84b6247c46e9c0dbe8502991e5f7edce672e5c66 Mon Sep 17 00:00:00 2001
From: Andreas Beckmann 
Date: Sun, 14 Mar 2021 05:25:53 +0100
Subject: [PATCH] fix package relationships

fix /usr/share/sane/xsane/xsane-startimage.pnm missing after
upgrading from buster to bullseye
---
 debian/changelog | 8 
 debian/control   | 5 -
 2 files changed, 12 insertions(+), 1 deletion(-)

diff --git a/debian/changelog b/debian/changelog
index 85c016d..a14db1f 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+xsane (0.999-10) UNRELEASED; urgency=medium
+
+  * xsane-common: Remove unversioned Replaces: xsane.
+  * xsane: Add Breaks+Replaces: xsane-common (<< 0.999-10~) for taking over
+xsane-startimage.pnm.  (Closes: #xx)
+
+ -- Andreas Beckmann   Sun, 14 Mar 2021 05:20:27 +0100
+
 xsane (0.999-9) unstable; urgency=medium
 
   * debian/copyright:
diff --git a/debian/control b/debian/control
index e5fa11d..741d763 100644
--- a/debian/control
+++ b/debian/control
@@ -34,6 +34,10 @@ Suggests:
  gocr | cuneiform | tesseract-ocr | ocrad,
  gv,
  hylafax-client | mgetty-fax
+Breaks:
+ xsane-common (<< 0.999-10~),
+Replaces:
+ xsane-common (<< 0.999-10~),
 Description: featureful graphical frontend for SANE (Scanner Access Now Easy)
  xsane can be run as a stand-alone program or through the GIMP image
  manipulation program.  In stand-alone mode, xsane can save an image
@@ -54,7 +58,6 @@ Package: xsane-common
 Architecture: all
 Multi-Arch: foreign
 Depends: ${misc:Depends}
-Replaces: xsane
 Recommends: xsane
 Description: xsane architecture independent files
  xsane can be run as a stand-alone program or through the GIMP image
-- 
2.20.1



xsane_0.999-9.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: xsane
Source-Version: 0.999-10
Done: Jörg Frings-Fürst 

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

Debian distribution maintenance software
pp.
Jörg Frings-Fürst  (supplier of updated xsane 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, 14 Mar 2021 11:34:10 +0100
Source: xsane
Architecture: source
Version: 0.999-10
Distribution: unstable
Urgency: medium
Maintainer: Jörg Frings-Fürst 
Changed-By: Jörg Frings-Fürst 
Closes: 985190
Changes:
 xsane (0.999-10) unstable; urgency=medium
 .
   * xsane-common: Remove unversioned Replaces: xsane.
   * xsane: Add Breaks+Replaces: xsane-common (<< 0.999-10~) for taking over
   xsane-startimage.pnm (Closes: #985190). Thanks to
   Andreas Beckmann .
   * debian/copyright:
 - Add year 2021 to debian/*.
   * Declare compliance with Debian Policy 4.5.1 (No changes needed).
Checksums-Sha1:
 2e5eba68b1878cc9ab671a03564bce6f5aa06848 1951 xsane_0.999-10.dsc
 390fab8c6d8505f36cb2732f5a2dac