Bug#859054: libpam-ssh: Please migrate to openssl1.1 in buster

[Jerome BENOIT]

Thanks for the remainder, I will have a look this week-end,
Jerome

On 19/12/2018 05:32, John Stamp wrote:
> On 05/22/18 08:52 PM, Jerome BENOIT wrote:
>> Hello,
>>
>>
>>
>> On 22/05/18 23:52, Moritz Muehlenhoff wrote:
>>> Hi Jerome,
>>>
>>> On Fri, Oct 13, 2017 at 07:05:26PM +0400, Jerome BENOIT wrote:
 Dear Sebastian, thanks for your warning.

 The amount of change might be too heavy for me.
 Second, pam_ssh seems no more maintained.

 I have just contacted the upstream maintainer.
>>>
>>> Did you get a reply?
>>
>> No.
>>
>> I will have a look if time permit.
>> And, of course, any patch is welcome.
>>
>> Cheers,
>> Jerome
> 
> OpenSUSE has an OpenSSL 1.1 patch in their package:
> 
>   
> https://build.opensuse.org/package/view_file/openSUSE:Factory/pam_ssh/pam_ssh-openssl11.patch
> 
> Changelog here:
> 
>   https://build.opensuse.org/request/show/547009
> 
> I'm attaching the patch.  It will try to modify `configure' which isn't
> in Debian's source tarball, but if you remove that bit, it applies
> cleanly.  It seems to work OK on my locally-built package.
> 
> John
> 

-- 
Jerome BENOIT | calculus+at-rezozer^dot*net
https://qa.debian.org/developer.php?login=calcu...@rezozer.net
AE28 AE15 710D FF1D 87E5  A762 3F92 19A6 7F36 C68B



signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#890117: bedtools FTBFS on big endian: Tools failing: bamtobed bamtofastq coverage genomecov groupby intersect jaccard map merge multicov negativecontrol

[Debian Bug Tracking System]

Processing control commands:

> tags -1 help
Bug #890117 [src:bedtools] bedtools FTBFS on big endian: Tools failing:  
bamtobed bamtofastq coverage genomecov groupby intersect jaccard map merge 
multicov negativecontrol
Added tag(s) help.
> tags -1 upstream
Bug #890117 [src:bedtools] bedtools FTBFS on big endian: Tools failing:  
bamtobed bamtofastq coverage genomecov groupby intersect jaccard map merge 
multicov negativecontrol
Added tag(s) upstream.
> forwarded -1 https://github.com/arq5x/bedtools2/issues/676
Bug #890117 [src:bedtools] bedtools FTBFS on big endian: Tools failing:  
bamtobed bamtofastq coverage genomecov groupby intersect jaccard map merge 
multicov negativecontrol
Set Bug forwarded-to-address to 'https://github.com/arq5x/bedtools2/issues/676'.

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

Bug#890117: bedtools FTBFS on big endian: Tools failing: bamtobed bamtofastq coverage genomecov groupby intersect jaccard map merge multicov negativecontrol

[Andreas Tille]

Control: tags -1 help
Control: tags -1 upstream
Control: forwarded -1 https://github.com/arq5x/bedtools2/issues/676


-- 
http://fam-tille.de

Processed: Re: Bug#890116: bedtools FTBFS on 32bit: Tools failing: coverage intersect negativecontrol reldist shuffle split

[Debian Bug Tracking System]

Processing control commands:

> tags -1 help
Bug #890116 [src:bedtools] bedtools FTBFS on 32bit: Tools failing:  coverage 
intersect negativecontrol reldist shuffle split
Added tag(s) help.
> tags -1 upstream
Bug #890116 [src:bedtools] bedtools FTBFS on 32bit: Tools failing:  coverage 
intersect negativecontrol reldist shuffle split
Added tag(s) upstream.
> forwarded -1 https://github.com/arq5x/bedtools2/issues/675
Bug #890116 [src:bedtools] bedtools FTBFS on 32bit: Tools failing:  coverage 
intersect negativecontrol reldist shuffle split
Set Bug forwarded-to-address to 'https://github.com/arq5x/bedtools2/issues/675'.

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

Bug#890116: bedtools FTBFS on 32bit: Tools failing: coverage intersect negativecontrol reldist shuffle split

[Andreas Tille]

Control: tags -1 help
Control: tags -1 upstream
Control: forwarded -1 https://github.com/arq5x/bedtools2/issues/675


-- 
http://fam-tille.de

Processed: Problem seem to occur rarely

[Debian Bug Tracking System]

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

> severity 671644 important
Bug #671644 [sympa] Password changed due to session/cookie problem
Severity set to 'important' from 'critical'
> thanks
Stopping processing here.

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

Bug#916737: marked as done (bcron: fails to install: installed bcron package post-installation script subprocess returned error exit status 1)

[Debian Bug Tracking System]

Your message dated Wed, 19 Dec 2018 07:19:30 +
with message-id 
and subject line Bug#916737: fixed in bcron 0.11-4
has caused the Debian Bug report #916737,
regarding bcron: fails to install: installed bcron package post-installation 
script subprocess returned error exit status 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.)


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

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

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

  Selecting previously unselected package bcron.
  (Reading database ... 
(Reading database ... 4540 files and directories currently installed.)
  Preparing to unpack .../bcron_0.11-3_amd64.deb ...
  Unpacking bcron (0.11-3) ...
  Setting up bcron (0.11-3) ...
  dpkg: error processing package bcron (--configure):
   installed bcron package post-installation script subprocess returned error 
exit status 1
  Errors were encountered while processing:
   bcron


cheers,

Andreas


bcron_0.11-3.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: bcron
Source-Version: 0.11-4

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

Debian distribution maintenance software
pp.
Dmitry Bogatov  (supplier of updated bcron 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: Wed, 19 Dec 2018 06:56:59 +
Source: bcron
Binary: bcron
Architecture: source
Version: 0.11-4
Distribution: experimental
Urgency: medium
Maintainer: Gerrit Pape 
Changed-By: Dmitry Bogatov 
Description:
 bcron  - Bruce cron system
Closes: 858505 916737
Changes:
 bcron (0.11-4) experimental; urgency=medium
 .
   * Build-Depends on latest version of dh-runit, that ensures
 presence of `/etc/runit/runsvdir/default' directory.
   * Fix `postinst' maintainer script (Closes: #916737)
   * Update Vcs-* fields in `debian/control'
   * Fix broken symlink (Closes: #858505)
   * Remove redundant sentence from package long description
Checksums-Sha1:
 6c9b82323fe64c61aa15b7fe116945b5fcb22a89 2115 bcron_0.11-4.dsc
 240b3a1c99681d62c03a3f5c7029db06003ea295 15712 bcron_0.11-4.debian.tar.xz
Checksums-Sha256:
 59304581eaa2317ddd0050e25f1de24631e976f412558752b0ae88a191926689 2115 
bcron_0.11-4.dsc
 04b6030c50af8e9edff49c3bc3188e431cac67e471ad4df50324cf6e8d075b3d 15712 
bcron_0.11-4.debian.tar.xz
Files:
 5cd7e2f56679ce2e058a4071aa91594c 2115 admin optional bcron_0.11-4.dsc
 66c2766d3decd1a2dfe2d860f0dd0d5e 15712 admin optional 
bcron_0.11-4.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJHBAEBCgAxFiEEhnHVzDbtdH7ktKj4SBLY3qgmEeYFAlwZ6/ATHGthY3Rpb25A
ZGViaWFuLm9yZwAKCRBIEtjeqCYR5qvoEAChjAdxg2IN19jkEUGHjzSExfmpUnV4
WvEEqdDE66w7y202H5x5UuLX9I6VSTa0MW16CbGnYaa/EgZ2JjYpgw5PDQQB+t2L
icYGqZQ7Erl4Z7t9fNKOC6OMW9WjNHmIxMJSYeuyXVU9t3kvRzWSTYiUIWfHx96s
3v+c9CT0z+MJ7gNK6aZ+tACAIyUNZDfoFClzAzFw4kSa5R7UKYmYVLcJ5p/8RbaM
2WR2ZschnRf2I1Wn9+yklzRUY+2JeAqSDTN6ERqH7aYehutyjo01HMeFkr4ykck8
4bQyBCE5rLPY4OnDDmNvlopeDyh4Q5ePRI1a2nBzRrbSnBaJTGgFWGd7FshvWz+E
B0OSDQNaQJk1Hu1wdK3qIcU+VOYGfMWWe+mWxv4RNUqzVlQysGpD6HUfPJmjSuDC
94rVBfcMlSbyaAvWqY1i1QgRJUHq9hsEwEdkuSM26Xyn/dffKYCavmHlQe14GVHM
ARwkgoGcDQ4lESSnUSDjFO8qxusLQUTDuziwmC+O1accJEag99nhfXtOLoPGlkJX
OVTE/W+aI+Ibpdur2w1oYJKaCfJJvKW6cpwumZ65SKwdBw/MH3Om0mb7ikqJOFNj
rXAhOl0PlEcnEy40ck5x7vgKiqQ9bDmkq9Xx915JZtE7WqJft2xrnISev0LeBZCI
dB9e4E42gAVtZA==
=3vQT
-END PGP SIGNATURE End Message ---

Bug#915690: marked as done (kvpm - Depends on deprecated liblvm2app)

[Debian Bug Tracking System]

Your message dated Wed, 19 Dec 2018 06:08:07 +
with message-id 
and subject line Bug#916802: Removed package(s) from unstable
has caused the Debian Bug report #915690,
regarding kvpm - Depends on deprecated liblvm2app
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.)


-- 
915690: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915690
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kvpm
Version: 0.9.10-1.1
Severity: serious

liblvm2app is deprecated and will be not longer shipped with Buster.
Please drop it's usage.

Further references are found here:
https://bugzilla.redhat.com/show_bug.cgi?id=1489590

Bastian

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-rc6-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages kvpm depends on:
ii  libblkid1   2.32.1-0.1
ii  libc6   2.27-8
ii  libdevmapper1.02.1  2:1.02.145-4.1
ii  libgcc1 1:8.2.0-9
pn  libkf5configcore5   
pn  libkf5configgui5
pn  libkf5configwidgets5
pn  libkf5coreaddons5   
pn  libkf5i18n5 
pn  libkf5kdelibs4support5  
pn  libkf5widgetsaddons5
pn  libkf5xmlgui5   
ii  liblvm2app2.2   2.02.176-4.1
ii  libparted2  3.2-23
ii  libqt5core5a5.11.2+dfsg-7
ii  libqt5gui5  5.11.2+dfsg-7
ii  libqt5widgets5  5.11.2+dfsg-7
ii  libstdc++6  8.2.0-9

Versions of packages kvpm recommends:
pn  dosfstools 
ii  e2fsprogs  1.44.4-2
pn  jfsutils   
pn  ntfs-3g
pn  reiserfsprogs  
pn  xfsprogs   

Versions of packages kvpm suggests:
ii  btrfs-progs   4.17-1
ii  btrfs-tools   4.15.1-2
pn  reiser4progs  
--- End Message ---
--- Begin Message ---
Version: 0.9.10-1.1+rm

Dear submitter,

as the package kvpm has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/916802

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#915996: marked as done (kvpm FTBFS with glibc 2.28)

[Debian Bug Tracking System]

Your message dated Wed, 19 Dec 2018 06:08:07 +
with message-id 
and subject line Bug#916802: Removed package(s) from unstable
has caused the Debian Bug report #915996,
regarding kvpm FTBFS with glibc 2.28
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.)


-- 
915996: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915996
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kvpm
Version: 0.9.10-1.1
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/kvpm.html

...
/build/1st/kvpm-0.9.10/kvpm/logvol.cpp: In member function 'void 
LogVol::getDeviceNumbers(long unsigned int&, long unsigned int&)':
/build/1st/kvpm-0.9.10/kvpm/logvol.cpp:1147:16: error: 'major' was not declared 
in this scope
 majornum = major(fs.st_rdev);
^
/build/1st/kvpm-0.9.10/kvpm/logvol.cpp:1148:16: error: 'minor' was not declared 
in this scope
 minornum = minor(fs.st_rdev);
^
--- End Message ---
--- Begin Message ---
Version: 0.9.10-1.1+rm

Dear submitter,

as the package kvpm has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/916802

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#868413: marked as done (gbonds: Please drop the (build-)dependency against gnome-vfs)

[Debian Bug Tracking System]

Your message dated Wed, 19 Dec 2018 04:04:18 +
with message-id 
and subject line Bug#868413: fixed in gbonds 2.0.3-12
has caused the Debian Bug report #868413,
regarding gbonds: Please drop the (build-)dependency against gnome-vfs
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.)


-- 
868413: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868413
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gbonds
Version: 2.0.3-9
Severity: wishlist
Tags: sid buster
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-vfs-removal oldlibs

Dear maintainer,

Your package is {build-}depending against gnome-vfs which is
deprecated for quite some times now and has been replaced by gvfs.

We are thinking about removing gnome-vfs for Buster if possible.

Could you please verify that this dependency is mandatory and if it's
not the case, could you please remove it?

Don't hesitate to contact me if you have any questions.

Kind regards,

Laurent Bigonville 
--- End Message ---
--- Begin Message ---
Source: gbonds
Source-Version: 2.0.3-12

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

Debian distribution maintenance software
pp.
Richard Laager  (supplier of updated gbonds 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: Tue, 18 Dec 2018 14:25:57 -0600
Source: gbonds
Binary: gbonds gbonds-data
Architecture: source
Version: 2.0.3-12
Distribution: unstable
Urgency: medium
Maintainer: Richard Laager 
Changed-By: Richard Laager 
Description:
 gbonds - U.S. Savings Bond inventory program for GNOME
 gbonds-data - GBonds data files
Closes: 868413 885638 886080
Changes:
 gbonds (2.0.3-12) unstable; urgency=medium
 .
   [ Richard Laager ]
   * Update Standards-Version to 4.2.1 (no changes)
   * Add redemption data through 05/2019 (sb201812.asc)
 .
   [ Yavor Doganov ]
   * Port to GTK+ 3 and GIO (Closes: 868413)
   * Port to GSettings (Closes: 886080)
   * Get rid of rarian-compat B-D (Closes: 885638)
   * Remove gnome-common B-D
Checksums-Sha1:
 355a2688cacbb3b99fed871889741ce6154c30fd 2027 gbonds_2.0.3-12.dsc
 531d3bb395344eae582d1b5a0eb76b0b0c19aac4 89548 gbonds_2.0.3-12.debian.tar.xz
 4a0d0d6f835cff2ca9bbec98a2df68b0539b30ee 15274 gbonds_2.0.3-12_amd64.buildinfo
Checksums-Sha256:
 25c2b5086c4fb1c7a042ffbedaeddd57a5d03684b2225ca6133749b7a0355f14 2027 
gbonds_2.0.3-12.dsc
 5adf36476a8073a2a0c7318d01e7567a25f10527e9b4cc504af503b3a056897f 89548 
gbonds_2.0.3-12.debian.tar.xz
 8b5780e97f9f17d03718a9997849ff3c283dfc378653f176c9a2f7d3ec3d508b 15274 
gbonds_2.0.3-12_amd64.buildinfo
Files:
 8bcf094963df82dc6669a34d004b71fd 2027 gnome optional gbonds_2.0.3-12.dsc
 ef6573c965e7b1ff91c9098ef058d093 89548 gnome optional 
gbonds_2.0.3-12.debian.tar.xz
 c88899c19f85ed922b5b453a896dff96 15274 gnome optional 
gbonds_2.0.3-12_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEE5Qr9Va3SequXFjqLIdIFiZdLPpYFAlwZvGgUHHRtYW5jaWxs
QGRlYmlhbi5vcmcACgkQIdIFiZdLPpbflxAAgbUIoPEt/v25HCIE8FqHnUrccwcb
60R8AO2Oewuawi/s7AYBVMUY9YarS8x5tdE/RWjN7v4YRzqIY+7ajv6ozx8TLMCU
wgRSyXTJSTwl72+JfXgUrTbmagVRv/trZQXeMrO95Zz7YxfnI7wXdT+wM3ano1cs
SSHKdC2JNhFH11hDj6ei9uPA/YHTH6TAb+0vGihB9SmAZ26Abs+Ogj+uZ6ksyMUV
eWSYGrR39w0PEZSbnUG8gj8syVb9I7Tw5sVtX9h7I2FxZV17NtRMAMH26TsXYLkd
hd30bd+ltkFlmf2t2Uyf+XQaK9Pno45KqfSRy+rnWedrvIhtNy8u+UFG90DiDMeq
oYc8ESR4REUXTmQuSdQMuox9qZONU9uDGc316xWgZL2Pm7JdNuooNHoL4sjk/WaM
LxXGWNYvhMe4DrTFc4/cUapRjirBFAxzmD7gF3lChpRgHkTXYtB1xebgYHuB6n/N
mvgElKtQUjC0AOIF48VZBsLzsnl5WiPeQffkQ70amBr9SQKPeG0z0cQDl8Rrpk2I
Q4bbKEA2yyRGeOWMxTtMSRUcA3WAHWdNzdsI6u8qVlGGwG9ooD6yCQnxfm7oRMzr
iYtvUVhl+jyjbFPDHH9pyjLAjygZWsgFeq6NPF833H/iPddz6OhX07orGMBS7KXu
NOOlDdu9/BlNZGE=
=dpmD
-END PGP SIGNATURE End Message ---

Bug#885638: marked as done (gbonds: Please drop Build-Depends on rarian-compat)

[Debian Bug Tracking System]

Your message dated Wed, 19 Dec 2018 04:04:18 +
with message-id 
and subject line Bug#885638: fixed in gbonds 2.0.3-12
has caused the Debian Bug report #885638,
regarding gbonds: Please drop Build-Depends on rarian-compat
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.)


-- 
885638: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885638
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gbonds
Version: 2.0.3-11
Severity: important
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs rarian
Tags: sid buster

scrollkeeper has been deprecated and unmaintained for years. Its
replacement, rarian has been deprecated for years too. More
importantly, it doesn't seem to be needed at all. yelp can easily
display Docbook help files without any .omf files.

We do not intend to ship rarian in Debian 10 "Buster". Therefore,
please drop rarian-compat from gbonds' Build-Depends.

On behalf of the Debian GNOME team,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: gbonds
Source-Version: 2.0.3-12

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

Debian distribution maintenance software
pp.
Richard Laager  (supplier of updated gbonds 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: Tue, 18 Dec 2018 14:25:57 -0600
Source: gbonds
Binary: gbonds gbonds-data
Architecture: source
Version: 2.0.3-12
Distribution: unstable
Urgency: medium
Maintainer: Richard Laager 
Changed-By: Richard Laager 
Description:
 gbonds - U.S. Savings Bond inventory program for GNOME
 gbonds-data - GBonds data files
Closes: 868413 885638 886080
Changes:
 gbonds (2.0.3-12) unstable; urgency=medium
 .
   [ Richard Laager ]
   * Update Standards-Version to 4.2.1 (no changes)
   * Add redemption data through 05/2019 (sb201812.asc)
 .
   [ Yavor Doganov ]
   * Port to GTK+ 3 and GIO (Closes: 868413)
   * Port to GSettings (Closes: 886080)
   * Get rid of rarian-compat B-D (Closes: 885638)
   * Remove gnome-common B-D
Checksums-Sha1:
 355a2688cacbb3b99fed871889741ce6154c30fd 2027 gbonds_2.0.3-12.dsc
 531d3bb395344eae582d1b5a0eb76b0b0c19aac4 89548 gbonds_2.0.3-12.debian.tar.xz
 4a0d0d6f835cff2ca9bbec98a2df68b0539b30ee 15274 gbonds_2.0.3-12_amd64.buildinfo
Checksums-Sha256:
 25c2b5086c4fb1c7a042ffbedaeddd57a5d03684b2225ca6133749b7a0355f14 2027 
gbonds_2.0.3-12.dsc
 5adf36476a8073a2a0c7318d01e7567a25f10527e9b4cc504af503b3a056897f 89548 
gbonds_2.0.3-12.debian.tar.xz
 8b5780e97f9f17d03718a9997849ff3c283dfc378653f176c9a2f7d3ec3d508b 15274 
gbonds_2.0.3-12_amd64.buildinfo
Files:
 8bcf094963df82dc6669a34d004b71fd 2027 gnome optional gbonds_2.0.3-12.dsc
 ef6573c965e7b1ff91c9098ef058d093 89548 gnome optional 
gbonds_2.0.3-12.debian.tar.xz
 c88899c19f85ed922b5b453a896dff96 15274 gnome optional 
gbonds_2.0.3-12_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEE5Qr9Va3SequXFjqLIdIFiZdLPpYFAlwZvGgUHHRtYW5jaWxs
QGRlYmlhbi5vcmcACgkQIdIFiZdLPpbflxAAgbUIoPEt/v25HCIE8FqHnUrccwcb
60R8AO2Oewuawi/s7AYBVMUY9YarS8x5tdE/RWjN7v4YRzqIY+7ajv6ozx8TLMCU
wgRSyXTJSTwl72+JfXgUrTbmagVRv/trZQXeMrO95Zz7YxfnI7wXdT+wM3ano1cs
SSHKdC2JNhFH11hDj6ei9uPA/YHTH6TAb+0vGihB9SmAZ26Abs+Ogj+uZ6ksyMUV
eWSYGrR39w0PEZSbnUG8gj8syVb9I7Tw5sVtX9h7I2FxZV17NtRMAMH26TsXYLkd
hd30bd+ltkFlmf2t2Uyf+XQaK9Pno45KqfSRy+rnWedrvIhtNy8u+UFG90DiDMeq
oYc8ESR4REUXTmQuSdQMuox9qZONU9uDGc316xWgZL2Pm7JdNuooNHoL4sjk/WaM
LxXGWNYvhMe4DrTFc4/cUapRjirBFAxzmD7gF3lChpRgHkTXYtB1xebgYHuB6n/N
mvgElKtQUjC0AOIF48VZBsLzsnl5WiPeQffkQ70amBr9SQKPeG0z0cQDl8Rrpk2I
Q4bbKEA2yyRGeOWMxTtMSRUcA3WAHWdNzdsI6u8qVlGGwG9ooD6yCQnxfm7oRMzr
iYtvUVhl+jyjbFPDHH9pyjLAjygZWsgFeq6NPF833H/iPddz6OhX07orGMBS7KXu
NOOlDdu9/BlNZGE=
=dpmD
-END PGP SIGNATURE End Message ---

Processed: found 886853 in 1:10.3.11-1~exp2

[Debian Bug Tracking System]

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

> found 886853 1:10.3.11-1~exp2
Bug #886853 [mariadb-plugin-rocksdb] mariadb-plugin-rocksdb: use sst_dump from 
rocksdb-tools
Marked as found in versions mariadb-10.3/1:10.3.11-1~exp2.
> thanks
Stopping processing here.

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

Bug#863675: libmariadbd-dev: fails to upgrade from 'sid' - trying to overwrite /usr/bin/mysql_config

[Andreas Beckmann]

Followup-For: Bug #863675

And another conflict:

  Preparing to unpack .../libmariadb-dev_1%3a10.3.11-1~exp2_amd64.deb ...
  Unpacking libmariadb-dev:amd64 (1:10.3.11-1~exp2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libmariadb-dev_1%3a10.3.11-1~exp2_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/libmysqlservices.a', which is 
also in package libmysqld-dev 5.7.24-2
  Errors were encountered while processing:
   /var/cache/apt/archives/libmariadb-dev_1%3a10.3.11-1~exp2_amd64.deb


Andreas

Bug#863675: libmariadbd-dev: fails to upgrade from 'sid' - trying to overwrite /usr/bin/mysql_config

[Andreas Beckmann]

Followup-For: Bug #863675
Control: found -1 1:10.3.11-1~exp2

  Preparing to unpack .../libmariadb-dev_1%3a10.3.11-1~exp2_amd64.deb ...
  Unpacking libmariadb-dev:amd64 (1:10.3.11-1~exp2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libmariadb-dev_1%3a10.3.11-1~exp2_amd64.deb (--unpack):
   trying to overwrite '/usr/share/aclocal/mysql.m4', which is also in package 
libmysqlclient-dev 5.7.24-2
  Errors were encountered while processing:
   /var/cache/apt/archives/libmariadb-dev_1%3a10.3.11-1~exp2_amd64.deb

The following files are in both libmysqlclient-dev/sid and 
libmariadb-dev/experimental:

usr/share/aclocal/mysql.m4
usr/share/man/man1/mysql_config.1.gz


Andreas

Processed: Re: libmariadbd-dev: fails to upgrade from 'sid' - trying to overwrite /usr/bin/mysql_config

[Debian Bug Tracking System]

Processing control commands:

> found -1 1:10.3.11-1~exp2
Bug #863675 [src:mariadb-10.3] libmariadbd-dev: fails to upgrade from 'sid' - 
trying to overwrite /usr/bin/mysql_config
Marked as found in versions mariadb-10.3/1:10.3.11-1~exp2.

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

Bug#916823: libmeep12: missing Breaks+Replaces: libmeep8

[Andreas Beckmann]

Package: libmeep12
Version: 1.7.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' 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 .../libmeep12_1.7.0-1_amd64.deb ...
  Unpacking libmeep12 (1.7.0-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libmeep12_1.7.0-1_amd64.deb (--unpack):
   trying to overwrite '/usr/share/meep/casimir.scm', which is also in package 
libmeep8 1.3-4+b4
  Errors were encountered while processing:
   /var/cache/apt/archives/libmeep12_1.7.0-1_amd64.deb


cheers,

Andreas


libmeep8=1.3-4+b4_libmeep12=1.7.0-1.log.gz
Description: application/gzip

Bug#859054: libpam-ssh: Please migrate to openssl1.1 in buster

[John Stamp]

On 05/22/18 08:52 PM, Jerome BENOIT wrote:
> Hello,
> 
> 
> 
> On 22/05/18 23:52, Moritz Muehlenhoff wrote:
> > Hi Jerome,
> > 
> > On Fri, Oct 13, 2017 at 07:05:26PM +0400, Jerome BENOIT wrote:
> >> Dear Sebastian, thanks for your warning.
> >>
> >> The amount of change might be too heavy for me.
> >> Second, pam_ssh seems no more maintained.
> >>
> >> I have just contacted the upstream maintainer.
> > 
> > Did you get a reply?
> 
> No.
> 
> I will have a look if time permit.
> And, of course, any patch is welcome.
> 
> Cheers,
> Jerome

OpenSUSE has an OpenSSL 1.1 patch in their package:

  
https://build.opensuse.org/package/view_file/openSUSE:Factory/pam_ssh/pam_ssh-openssl11.patch

Changelog here:

  https://build.opensuse.org/request/show/547009

I'm attaching the patch.  It will try to modify `configure' which isn't
in Debian's source tarball, but if you remove that bit, it applies
cleanly.  It seems to work OK on my locally-built package.

John

===
Index: pam_ssh-2.1/cipher.c
===
--- pam_ssh-2.1.orig/cipher.c	2015-05-03 13:30:39.0 +0200
+++ pam_ssh-2.1/cipher.c	2017-11-30 15:31:05.770390639 +0100
@@ -326,26 +326,26 @@ cipher_init(struct sshcipher_ctx *cc, co
 	return SSH_ERR_INVALID_ARGUMENT;
 #else
 	type = (*cipher->evptype)();
-	EVP_CIPHER_CTX_init(>evp);
-	if (EVP_CipherInit(>evp, type, NULL, (u_char *)iv,
+	cc->evp = EVP_CIPHER_CTX_new();
+	if (EVP_CipherInit(cc->evp, type, NULL, (u_char *)iv,
 	(do_encrypt == CIPHER_ENCRYPT)) == 0) {
 		ret = SSH_ERR_LIBCRYPTO_ERROR;
 		goto bad;
 	}
 	if (cipher_authlen(cipher) &&
-	!EVP_CIPHER_CTX_ctrl(>evp, EVP_CTRL_GCM_SET_IV_FIXED,
+	!EVP_CIPHER_CTX_ctrl(cc->evp, EVP_CTRL_GCM_SET_IV_FIXED,
 	-1, (u_char *)iv)) {
 		ret = SSH_ERR_LIBCRYPTO_ERROR;
 		goto bad;
 	}
-	klen = EVP_CIPHER_CTX_key_length(>evp);
+	klen = EVP_CIPHER_CTX_key_length(cc->evp);
 	if (klen > 0 && keylen != (u_int)klen) {
-		if (EVP_CIPHER_CTX_set_key_length(>evp, keylen) == 0) {
+		if (EVP_CIPHER_CTX_set_key_length(cc->evp, keylen) == 0) {
 			ret = SSH_ERR_LIBCRYPTO_ERROR;
 			goto bad;
 		}
 	}
-	if (EVP_CipherInit(>evp, NULL, (u_char *)key, NULL, -1) == 0) {
+	if (EVP_CipherInit(cc->evp, NULL, (u_char *)key, NULL, -1) == 0) {
 		ret = SSH_ERR_LIBCRYPTO_ERROR;
 		goto bad;
 	}
@@ -358,14 +358,14 @@ cipher_init(struct sshcipher_ctx *cc, co
 			ret = SSH_ERR_ALLOC_FAIL;
 			goto bad;
 		}
-		ret = EVP_Cipher(>evp, discard, junk, cipher->discard_len);
+		ret = EVP_Cipher(cc->evp, discard, junk, cipher->discard_len);
 		explicit_bzero(discard, cipher->discard_len);
 		free(junk);
 		free(discard);
 		if (ret != 1) {
 			ret = SSH_ERR_LIBCRYPTO_ERROR;
  bad:
-			EVP_CIPHER_CTX_cleanup(>evp);
+			EVP_CIPHER_CTX_cleanup(cc->evp);
 			return ret;
 		}
 	}
@@ -412,33 +412,33 @@ cipher_crypt(struct sshcipher_ctx *cc, u
 		if (authlen != cipher_authlen(cc->cipher))
 			return SSH_ERR_INVALID_ARGUMENT;
 		/* increment IV */
-		if (!EVP_CIPHER_CTX_ctrl(>evp, EVP_CTRL_GCM_IV_GEN,
+		if (!EVP_CIPHER_CTX_ctrl(cc->evp, EVP_CTRL_GCM_IV_GEN,
 		1, lastiv))
 			return SSH_ERR_LIBCRYPTO_ERROR;
 		/* set tag on decyption */
 		if (!cc->encrypt &&
-		!EVP_CIPHER_CTX_ctrl(>evp, EVP_CTRL_GCM_SET_TAG,
+		!EVP_CIPHER_CTX_ctrl(cc->evp, EVP_CTRL_GCM_SET_TAG,
 		authlen, (u_char *)src + aadlen + len))
 			return SSH_ERR_LIBCRYPTO_ERROR;
 	}
 	if (aadlen) {
 		if (authlen &&
-		EVP_Cipher(>evp, NULL, (u_char *)src, aadlen) < 0)
+		EVP_Cipher(cc->evp, NULL, (u_char *)src, aadlen) < 0)
 			return SSH_ERR_LIBCRYPTO_ERROR;
 		memcpy(dest, src, aadlen);
 	}
 	if (len % cc->cipher->block_size)
 		return SSH_ERR_INVALID_ARGUMENT;
-	if (EVP_Cipher(>evp, dest + aadlen, (u_char *)src + aadlen,
+	if (EVP_Cipher(cc->evp, dest + aadlen, (u_char *)src + aadlen,
 	len) < 0)
 		return SSH_ERR_LIBCRYPTO_ERROR;
 	if (authlen) {
 		/* compute tag (on encrypt) or verify tag (on decrypt) */
-		if (EVP_Cipher(>evp, NULL, NULL, 0) < 0)
+		if (EVP_Cipher(cc->evp, NULL, NULL, 0) < 0)
 			return cc->encrypt ?
 			SSH_ERR_LIBCRYPTO_ERROR : SSH_ERR_MAC_INVALID;
 		if (cc->encrypt &&
-		!EVP_CIPHER_CTX_ctrl(>evp, EVP_CTRL_GCM_GET_TAG,
+		!EVP_CIPHER_CTX_ctrl(cc->evp, EVP_CTRL_GCM_GET_TAG,
 		authlen, dest + aadlen + len))
 			return SSH_ERR_LIBCRYPTO_ERROR;
 	}
@@ -471,7 +471,7 @@ cipher_cleanup(struct sshcipher_ctx *cc)
 	else if ((cc->cipher->flags & CFLAG_AESCTR) != 0)
 		explicit_bzero(>ac_ctx, sizeof(cc->ac_ctx));
 #ifdef WITH_OPENSSL
-	else if (EVP_CIPHER_CTX_cleanup(>evp) == 0)
+	else if (EVP_CIPHER_CTX_cleanup(cc->evp) == 0)
 		return SSH_ERR_LIBCRYPTO_ERROR;
 #endif
 	return 0;
@@ -518,7 +518,7 @@ cipher_get_keyiv_len(const struct sshcip
 		ivlen = 0;
 #ifdef WITH_OPENSSL
 	else
-		ivlen = EVP_CIPHER_CTX_iv_length(>evp);
+		ivlen = EVP_CIPHER_CTX_iv_length(cc->evp);
 #endif /* WITH_OPENSSL */
 	return (ivlen);
 }
@@ -544,7 +544,7 @@ 

Bug#916767: marked as done (python-dmidecode-data: missing Breaks+Replaces: python-dmidecode (<< 3.12.2-5))

[Debian Bug Tracking System]

Your message dated Wed, 19 Dec 2018 01:19:58 +
with message-id 
and subject line Bug#916767: fixed in python-dmidecode 3.12.2-6
has caused the Debian Bug report #916767,
regarding python-dmidecode-data: missing Breaks+Replaces: python-dmidecode (<< 
3.12.2-5)
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.)


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

Hi,

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

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

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

  Preparing to unpack .../python-dmidecode-data_3.12.2-5_all.deb ...
  Unpacking python-dmidecode-data (3.12.2-5) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python-dmidecode-data_3.12.2-5_all.deb (--unpack):
   trying to overwrite '/usr/share/python-dmidecode/pymap.xml', which is also 
in package python-dmidecode 3.12.2-4
  Errors were encountered while processing:
   /var/cache/apt/archives/python-dmidecode-data_3.12.2-5_all.deb


cheers,

Andreas


python-dmidecode=3.12.2-4_python-dmidecode-data=3.12.2-5.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: python-dmidecode
Source-Version: 3.12.2-6

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated python-dmidecode 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: Tue, 18 Dec 2018 19:50:28 -0500
Source: python-dmidecode
Binary: python-dmidecode python3-dmidecode python-dmidecode-dbg 
python3-dmidecode-dbg python-dmidecode-data
Architecture: source all amd64
Version: 3.12.2-6
Distribution: unstable
Urgency: medium
Maintainer: Sandro Tosi 
Changed-By: Sandro Tosi 
Description:
 python-dmidecode - Python extension module for dmidecode
 python-dmidecode-data - Python extension module for dmidecode (debug) - Data
 python-dmidecode-dbg - Python extension module for dmidecode (debug)
 python3-dmidecode - Python extension module for dmidecode - Python 3
 python3-dmidecode-dbg - Python extension module for dmidecode (debug) - Python 
3
Closes: 916767
Changes:
 python-dmidecode (3.12.2-6) unstable; urgency=medium
 .
   * add breaks+replace for -data; Closes: #916767
Checksums-Sha1:
 ebc9f6b616aea027354fb3fbbaecb9e75af8ab33 2461 python-dmidecode_3.12.2-6.dsc
 a6bd483f2daa457d378b0638b9b133f0fea94e4d 6852 
python-dmidecode_3.12.2-6.debian.tar.xz
 5cc5941661efcb8ab3b82c6ad373c499fc4c2384 22660 
python-dmidecode-data_3.12.2-6_all.deb
 1822dde9f94820ea85c3fad5ff876fada1f17a42 267932 
python-dmidecode-dbg_3.12.2-6_amd64.deb
 74d7a1b001ceaa4ef18728480ed87f7e48ec29b8 9967 
python-dmidecode_3.12.2-6_amd64.buildinfo
 00e2bb2451f2b839501445360f090c2f49dff5d9 74952 
python-dmidecode_3.12.2-6_amd64.deb
 67f8a64c5a0c2546a7c30e16ed65ca95becc4516 493764 
python3-dmidecode-dbg_3.12.2-6_amd64.deb
 d1eaee249e91ce2a69d9824936fa2cc07ce15b05 74996 
python3-dmidecode_3.12.2-6_amd64.deb
Checksums-Sha256:
 509d111c2f5b73b82d3dea22813b57ab64dfbf0875065aff6d1f612f2f35e0d0 2461 
python-dmidecode_3.12.2-6.dsc
 2ddbb52c0c146854a2c1147b36a6b123d634d561b19d033c0c2bce3bc0f32aec 6852 
python-dmidecode_3.12.2-6.debian.tar.xz
 53d9fd4f0638289d49a01fbb1dabb0c1bd826b39824174336684099c3e72095c 22660 
python-dmidecode-data_3.12.2-6_all.deb
 534a4045009c392bf714f9a3403ec0e8ec6827266d70978e4af617c7ab589b54 267932 
python-dmidecode-dbg_3.12.2-6_amd64.deb
 72dd6e9a1c12efa638be0a28c45be20604383a28083cabfa6a81f6cac62b6f55 9967 
python-dmidecode_3.12.2-6_amd64.buildinfo
 

Processed: Re: galera-3 FTBFS: error: no matching function for call to 'asio::ssl::context::context(asio::io_service&, asio::ssl::context_base::method)'

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #914112 [src:galera-3] galera-3 FTBFS: error: no matching function for call 
to 'asio::ssl::context::context(asio::io_service&, 
asio::ssl::context_base::method)'
Added tag(s) patch.

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

Bug#914112: galera-3 FTBFS: error: no matching function for call to 'asio::ssl::context::context(asio::io_service&, asio::ssl::context_base::method)'

[Logan Rosen]

Control: tags -1 patch

Dear Maintainer,

In Ubuntu, the attached patch was applied to achieve the following:

  * debian/rules: Use bundled asio, since system asio is too new (> 1.10.8).
  * debian/control: Remove build-dependency of libasio-dev (for now).

Thanks for considering the patch.

Logan

-- System Information:
Debian Release: buster/sid
  APT prefers cosmic-updates
  APT policy: (500, 'cosmic-updates'), (500, 'cosmic-security'), (500, 
'cosmic'), (400, 'cosmic-proposed'), (100, 'cosmic-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.18.0-12-generic (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru galera-3-25.3.24/debian/control galera-3-25.3.24/debian/control
--- galera-3-25.3.24/debian/control 2018-10-15 09:23:16.0 -0400
+++ galera-3-25.3.24/debian/control 2018-11-17 20:37:31.0 -0500
@@ -6,7 +6,6 @@
 Standards-Version: 4.2.1
 Build-Depends: check,
debhelper (>= 9.20151219~),
-   libasio-dev,
libboost-dev (>= 1.41),
libboost-program-options-dev (>= 1.41),
libssl-dev,
diff -Nru galera-3-25.3.24/debian/rules galera-3-25.3.24/debian/rules
--- galera-3-25.3.24/debian/rules   2018-10-15 04:27:36.0 -0400
+++ galera-3-25.3.24/debian/rules   2018-11-17 20:36:49.0 -0500
@@ -3,6 +3,9 @@
 DPKG_EXPORT_BUILDFLAGS = 1
 include /usr/share/dpkg/default.mk
 
+# Use bundled asio, since system asio is too new (> 1.10.8)
+SCONS_ARGS += system_asio=0
+
 # Parallel build support as adviced
 # at 
https://www.debian.org/doc/debian-policy/ch-source.html#s-debianrules-options
 ifneq (,$(filter parallel=%,$(DEB_BUILD_OPTIONS)))

Bug#915050: (gitlab) Re: Bug#915050: Keep out of testing

[Dominik George]

>> We had volatile, which, redefined properly, could help. I am trying
>to draft such a definition.
>
>Did you get a chance to work on it?

I do have this on my todo list for around Christmas.

People who know me that I deliberately leave out the year, but my intentions 
are 2018 ;).

-nik

Processed: Re: Bug#916768: libelogind-dev-doc: missing Breaks+Replaces: libelogind-dev (<< 239.1+20181115-1)

[Debian Bug Tracking System]

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

> package libelogind-dev-doc
Limiting to bugs with field 'package' containing at least one of 
'libelogind-dev-doc'
Limit currently set to 'package':'libelogind-dev-doc'

> tags 916768 + pending
Bug #916768 [libelogind-dev-doc] libelogind-dev-doc: missing Breaks+Replaces: 
libelogind-dev (<< 239.1+20181115-1)
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: 0.15.0 adds Python 3.7 support

[Debian Bug Tracking System]

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

> tags 913044 fixed-upstream
Bug #913044 [src:hy] hy fails its tests with Python3.7
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Bug#916768: libelogind-dev-doc: missing Breaks+Replaces: libelogind-dev (<< 239.1+20181115-1)

[Mark Hindley]

Package: libelogind-dev-doc
Tags: pending

On Tue, Dec 18, 2018 at 01:21:47PM +0100, Andreas Beckmann wrote:
> Package: libelogind-dev-doc
> Version: 239.3-3+debian1
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
> 
> Hi,
> 
> during a test with piuparts I noticed your package fails to upgrade from
> 'testing'.
> It installed fine in 'testing', then the upgrade to 'sid' fails
> because it tries to overwrite other packages files without declaring a
> Breaks+Replaces relation.

Andreas,

Many thanks. I have queued a fix for this.

> PS: please use a normal debian revision in the version, i.e. only number

This is deliberate: Devuan is the defacto packaging upstream for these packages
and therefore has the plain number only revision. We need to distinguish the
versions that include the Debian specific packaging.

Mark

Bug#916606: (no subject)

[bitfreak25]

Hi,

I've tried to create a backtrace for further investigation. This was done by 
setting a breakpoint at function client_set_pause() where the bug must occur. 
Then I've started the game an tried to reproduce the bug (the unwanted pause).

After I've got into the bug I must kill the lbreakout2 process through tty. 
Otherwise I've got a freezing display.

The created backtrace is attached.


Kind regards,
bitfreak25
GNU gdb (Debian 8.2-1) 8.2
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from lbreakout2...Reading symbols from 
/usr/lib/debug/.build-id/da/ba5499ea59ec74b5eaf7ee7da4a82f7069d508.debug...done.
done.
(gdb) break game.c:529
Breakpoint 1 at 0x1c410: file game.c, line 530.
(gdb) run
Starting program: /usr/games/lbreakout2 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7f1a98f2d700 (LWP 1762)]
[New Thread 0x7f1a944a8700 (LWP 1763)]
[Thread 0x7f1a944a8700 (LWP 1763) exited]
[New Thread 0x7f1a944a8700 (LWP 1764)]
Keine Schreibberechtigung fuer "/var/games/lbreakout2.hscr".
Kann Bestenliste unter "/var/games" nicht oeffnen!
Versuche Einstellungsverzeichnis "/home/user/.lgames" zu verwenden.

Thread 1 "lbreakout2" hit Breakpoint 1, client_set_pause (pause=1)
at game.c:531
531 game.c: Datei oder Verzeichnis nicht gefunden.
(gdb) bt
#0  client_set_pause (pause=1) at game.c:531
#1  0x56091057dd6a in handle_default_key (abort=, 
key=) at game.c:628
#2  client_game_run () at game.c:1161
Backtrace stopped: Cannot access memory at address 0x7ffd162af6b8
(gdb) bt full
#0  client_set_pause (pause=1) at game.c:531
No locals.
#1  0x56091057dd6a in handle_default_key (abort=, 
key=) at game.c:628
buffer = 
buffer = 
#2  client_game_run () at game.c:1161
ms = 1
frame_delay = 1
button_clicked = 0
key_pressed = 
event = 
abort = 0
i = 
j = 
penalty = 
frames = 24822
frame_time = 
Backtrace stopped: Cannot access memory at address 0x7ffd162af6b8

Bug#915050: (gitlab) Re: Bug#915050: Keep out of testing

[Dmitry Smirnov]

On Wednesday, 19 December 2018 9:17:51 AM AEDT Thorsten Glaser wrote:
> Did you mean: in an unstable-like “volatile” repo?

Yes perhaps more like "unstable".
I'm saying that IMHO we should have only one common/shared "PPA" for "stable" 
users. I do not want many personal/individual archives.


> Backports have a defined mission, which has nothing to do
> with the “volatile” proposal. What you were referring to,
> integration- and checks-wise, is, I think what you get in
> *any* repository maintained by ftpmasters, so it’d be more
> like sid, except only a partial distribution (add-on).

I also think that we could just relax official "backports" criteria but that 
would be so hard that it seem easier to arrange another "volatile" repo...

-- 
Regards,
 Dmitry Smirnov.

---

Success consists of going from failure to failure without loss of enthusiasm.
-- Winston Churchill


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

Bug#916800: phybin: FTBFS with newer GHC

[Andreas Tille]

Hi Joachim,

On Tue, Dec 18, 2018 at 10:57:15PM +0100, Joachim Breitner wrote:
> Would not be hard to fix, but is there a chance that upstream could just 
> release a version that works with a current compiler?

I'm afraid upstream is not very active but would be happy about a patch.

Kind regards

 Andreas.

-- 
http://fam-tille.de

Bug#915050: (gitlab) Re: Bug#915050: Keep out of testing

[Thorsten Glaser]

On Wed, 19 Dec 2018, Dmitry Smirnov wrote:

> trust - a something we can only have in backports-like "volatile" repo.

Did you mean: in an unstable-like “volatile” repo?

Backports have a defined mission, which has nothing to do
with the “volatile” proposal. What you were referring to,
integration- and checks-wise, is, I think what you get in
*any* repository maintained by ftpmasters, so it’d be more
like sid, except only a partial distribution (add-on).

bye,
//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

Bug#915050: (gitlab) Re: Bug#915050: Keep out of testing

[Dmitry Smirnov]

On Wednesday, 19 December 2018 2:11:43 AM AEDT Holger Levsen wrote:
> instead of volatile we need PPAs.

I think concept of "volatile" is better, stronger.
PPA allows people to ship whatever they want without cooperating in policy 
compliant (official) repo. This is the Debian way where many people work 
together in one centralized resource.
Many people working in many places (PPA) will undermine cooperativeness and 
trust - a something we can only have in backports-like "volatile" repo.

-- 
Cheers,
 Dmitry Smirnov.

---

The great enemy of the truth is very often not the lie -- deliberate,
contrived and dishonest, but the myth, persistent, persuasive, and
unrealistic. Belief in myths allows the comfort of opinion without the
discomfort of thought.
-- John F Kennedy


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

Processed: Re: Bug#916114: xawtv FTBFS with glibc 2.28

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + fixed-upstream
Bug #916114 [src:xawtv] xawtv FTBFS with glibc 2.28
Added tag(s) fixed-upstream.

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

Bug#916114: xawtv FTBFS with glibc 2.28

[Juhani Numminen]

Control: tags -1 + fixed-upstream

On Mon, 10 Dec 2018 12:29:10 +0200 Adrian Bunk  wrote:
> Source: xawtv
> Version: 3.104-1
> Severity: serious
> Tags: ftbfs
> 
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/xawtv.html
> ...
> ./common/get_media_devices.c:522: undefined reference to `major'
> /usr/bin/ld: ./common/get_media_devices.c:523: undefined reference to `minor'

Looks like there is an upstream commit to fix this:
https://git.linuxtv.org/xawtv3.git/commit/?id=65a71c3a0f36287402c0a959475fc0bc2eb46586

--
Juhani

Bug#916800: phybin: FTBFS with newer GHC

[Joachim Breitner]

Hi,

Would not be hard to fix, but is there a chance that upstream could just 
release a version that works with a current compiler?

Cheers, Joachim



Am 18. Dezember 2018 22:36:26 MEZ schrieb Andreas Tille :
>Control: tags -1 help
>
>Hi,
>
>unfortunately I have no idea how to fix this.
>
>Kind regards, Andreas.
>
>On Tue, Dec 18, 2018 at 08:32:22PM +0200, Ilias Tsitsimpis wrote:
>> Package: phybin
>> Version: 0.3-2
>> Severity: serious
>> Justification: fails to build from source (but built successfully in
>the past)
>> 
>> Dear maintainer,
>> 
>> phybin FTBFS with newer versions of GHC (>= 8.4) with the following
>error:
>> 
>>  [1 of 9] Compiling Bio.Phylogeny.PhyBin.CoreTypes (
>Bio/Phylogeny/PhyBin/CoreTypes.hs,
>dist-ghc/build/test-phybin/test-phybin-tmp/Bio/Phylogeny/PhyBin/CoreTypes.o
>)
>> 
>>  Bio/Phylogeny/PhyBin/CoreTypes.hs:112:35: error:
>>  Ambiguous occurrence `<>'
>>  It could refer to either `Prelude.<>',
>>   imported from 
>> `Prelude' at
>Bio/Phylogeny/PhyBin/CoreTypes.hs:7:8-37
>>   (and 
>> originally defined in `GHC.Base')
>>or 
>> `Text.PrettyPrint.HughesPJClass.<>',
>>   imported from 
>> `Text.PrettyPrint.HughesPJClass' at
>Bio/Phylogeny/PhyBin/CoreTypes.hs:40:1-58
>>   (and 
>> originally defined in
>`pretty-1.1.3.6:Text.PrettyPrint.HughesPJ')
>>  |
>>  112 | displayDefaultTree orig = loop tr <> ";"
>>  |   ^^
>> 
>>  Bio/Phylogeny/PhyBin/CoreTypes.hs:120:27: error:
>>  Ambiguous occurrence `<>'
>>  It could refer to either `Prelude.<>',
>>   imported from 
>> `Prelude' at
>Bio/Phylogeny/PhyBin/CoreTypes.hs:7:8-37
>>   (and 
>> originally defined in `GHC.Base')
>>or 
>> `Text.PrettyPrint.HughesPJClass.<>',
>>   imported from 
>> `Text.PrettyPrint.HughesPJClass' at
>Bio/Phylogeny/PhyBin/CoreTypes.hs:40:1-58
>>   (and 
>> originally defined in
>`pretty-1.1.3.6:Text.PrettyPrint.HughesPJ')
>>  |
>>  120 |  Just val -> base <> text ":[" <> text (show val) <>
>text "]"
>>  |   ^^
>> 
>>  Bio/Phylogeny/PhyBin/CoreTypes.hs:120:40: error:
>>  Ambiguous occurrence `<>'
>>  It could refer to either `Prelude.<>',
>>   imported from 
>> `Prelude' at
>Bio/Phylogeny/PhyBin/CoreTypes.hs:7:8-37
>>   (and 
>> originally defined in `GHC.Base')
>>or 
>> `Text.PrettyPrint.HughesPJClass.<>',
>>   imported from 
>> `Text.PrettyPrint.HughesPJClass' at
>Bio/Phylogeny/PhyBin/CoreTypes.hs:40:1-58
>>   (and 
>> originally defined in
>`pretty-1.1.3.6:Text.PrettyPrint.HughesPJ')
>>  |
>>  120 |  Just val -> base <> text ":[" <> text (show val) <>
>text "]"
>>  |^^
>> 
>>  Bio/Phylogeny/PhyBin/CoreTypes.hs:120:59: error:
>>  Ambiguous occurrence `<>'
>>  It could refer to either `Prelude.<>',
>>   imported from 
>> `Prelude' at
>Bio/Phylogeny/PhyBin/CoreTypes.hs:7:8-37
>>   (and 
>> originally defined in `GHC.Base')
>>or 
>> `Text.PrettyPrint.HughesPJClass.<>',
>>   imported from 
>> `Text.PrettyPrint.HughesPJClass' at
>Bio/Phylogeny/PhyBin/CoreTypes.hs:40:1-58
>>   (and 
>> originally defined in
>`pretty-1.1.3.6:Text.PrettyPrint.HughesPJ')
>>  |
>>  120 |  Just val -> base <> text ":[" <> text (show val) <>
>text "]"
>>  |   ^^
>> 
>>  Bio/Phylogeny/PhyBin/CoreTypes.hs:121:47: error:
>>  Ambiguous occurrence `<>'
>>  It could refer to either `Prelude.<>',
>>   imported from 
>> `Prelude' at
>Bio/Phylogeny/PhyBin/CoreTypes.hs:7:8-37
>> 

Processed: Re: Bug#916800: phybin: FTBFS with newer GHC

[Debian Bug Tracking System]

Processing control commands:

> tags -1 help
Bug #916800 [phybin] phybin: FTBFS with newer GHC
Added tag(s) help.

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

Bug#916800: phybin: FTBFS with newer GHC

[Andreas Tille]

Control: tags -1 help

Hi,

unfortunately I have no idea how to fix this.

Kind regards, Andreas.

On Tue, Dec 18, 2018 at 08:32:22PM +0200, Ilias Tsitsimpis wrote:
> Package: phybin
> Version: 0.3-2
> Severity: serious
> Justification: fails to build from source (but built successfully in the past)
> 
> Dear maintainer,
> 
> phybin FTBFS with newer versions of GHC (>= 8.4) with the following error:
> 
>   [1 of 9] Compiling Bio.Phylogeny.PhyBin.CoreTypes ( 
> Bio/Phylogeny/PhyBin/CoreTypes.hs, 
> dist-ghc/build/test-phybin/test-phybin-tmp/Bio/Phylogeny/PhyBin/CoreTypes.o )
> 
>   Bio/Phylogeny/PhyBin/CoreTypes.hs:112:35: error:
>   Ambiguous occurrence `<>'
>   It could refer to either `Prelude.<>',
>imported from 
> `Prelude' at Bio/Phylogeny/PhyBin/CoreTypes.hs:7:8-37
>(and 
> originally defined in `GHC.Base')
> or 
> `Text.PrettyPrint.HughesPJClass.<>',
>imported from 
> `Text.PrettyPrint.HughesPJClass' at Bio/Phylogeny/PhyBin/CoreTypes.hs:40:1-58
>(and 
> originally defined in `pretty-1.1.3.6:Text.PrettyPrint.HughesPJ')
>   |
>   112 | displayDefaultTree orig = loop tr <> ";"
>   |   ^^
> 
>   Bio/Phylogeny/PhyBin/CoreTypes.hs:120:27: error:
>   Ambiguous occurrence `<>'
>   It could refer to either `Prelude.<>',
>imported from 
> `Prelude' at Bio/Phylogeny/PhyBin/CoreTypes.hs:7:8-37
>(and 
> originally defined in `GHC.Base')
> or 
> `Text.PrettyPrint.HughesPJClass.<>',
>imported from 
> `Text.PrettyPrint.HughesPJClass' at Bio/Phylogeny/PhyBin/CoreTypes.hs:40:1-58
>(and 
> originally defined in `pretty-1.1.3.6:Text.PrettyPrint.HughesPJ')
>   |
>   120 |  Just val -> base <> text ":[" <> text (show val) <> text 
> "]"
>   |   ^^
> 
>   Bio/Phylogeny/PhyBin/CoreTypes.hs:120:40: error:
>   Ambiguous occurrence `<>'
>   It could refer to either `Prelude.<>',
>imported from 
> `Prelude' at Bio/Phylogeny/PhyBin/CoreTypes.hs:7:8-37
>(and 
> originally defined in `GHC.Base')
> or 
> `Text.PrettyPrint.HughesPJClass.<>',
>imported from 
> `Text.PrettyPrint.HughesPJClass' at Bio/Phylogeny/PhyBin/CoreTypes.hs:40:1-58
>(and 
> originally defined in `pretty-1.1.3.6:Text.PrettyPrint.HughesPJ')
>   |
>   120 |  Just val -> base <> text ":[" <> text (show val) <> text 
> "]"
>   |^^
> 
>   Bio/Phylogeny/PhyBin/CoreTypes.hs:120:59: error:
>   Ambiguous occurrence `<>'
>   It could refer to either `Prelude.<>',
>imported from 
> `Prelude' at Bio/Phylogeny/PhyBin/CoreTypes.hs:7:8-37
>(and 
> originally defined in `GHC.Base')
> or 
> `Text.PrettyPrint.HughesPJClass.<>',
>imported from 
> `Text.PrettyPrint.HughesPJClass' at Bio/Phylogeny/PhyBin/CoreTypes.hs:40:1-58
>(and 
> originally defined in `pretty-1.1.3.6:Text.PrettyPrint.HughesPJ')
>   |
>   120 |  Just val -> base <> text ":[" <> text (show val) <> text 
> "]"
>   |   ^^
> 
>   Bio/Phylogeny/PhyBin/CoreTypes.hs:121:47: error:
>   Ambiguous occurrence `<>'
>   It could refer to either `Prelude.<>',
>imported from 
> `Prelude' at Bio/Phylogeny/PhyBin/CoreTypes.hs:7:8-37
>(and 
> originally defined in `GHC.Base')
> or 
> `Text.PrettyPrint.HughesPJClass.<>',
>imported from 
> 

Bug#916559: marked as done (python3-ow{,net}: fails to install: SyntaxError in File "/usr/lib/python3/dist-packages/ow/__init__.py", line 346)

[Debian Bug Tracking System]

Your message dated Tue, 18 Dec 2018 21:26:32 +
with message-id 
and subject line Bug#916559: fixed in owfs 3.2p3+dfsg1-2
has caused the Debian Bug report #916559,
regarding python3-ow{,net}: fails to install: SyntaxError in File 
"/usr/lib/python3/dist-packages/ow/__init__.py", line 346
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.)


-- 
916559: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916559
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-ow,python3-ownet
Version: 3.2p3+dfsg1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

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

  Setting up python3-ow (3.2p3+dfsg1-1) ...
File "/usr/lib/python3/dist-packages/ow/__init__.py", line 346
  raise AttributeError, name
  ^
  SyntaxError: invalid syntax
  
  dpkg: error processing package python3-ow (--configure):
   installed python3-ow package post-installation script subprocess returned 
error exit status 1
  Processing triggers for libc-bin (2.28-2) ...
  Errors were encountered while processing:
   python3-ow


  Setting up python3-ownet (3.2p3+dfsg1-1) ...
File "/usr/lib/python3/dist-packages/ownet/__init__.py", line 251
  raise AttributeError, name
  ^
  SyntaxError: invalid syntax
  
File "/usr/lib/python3/dist-packages/ownet/connection.py", line 227
  raise exInvalidMessage, msg
^
  SyntaxError: invalid syntax
  
  dpkg: error processing package python3-ownet (--configure):
   installed python3-ownet package post-installation script subprocess returned 
error exit status 1
  Processing triggers for libc-bin (2.28-2) ...
  Errors were encountered while processing:


cheers,

Andreas


python3-ow_3.2p3+dfsg1-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: owfs
Source-Version: 3.2p3+dfsg1-2

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

Debian distribution maintenance software
pp.
Vincent Danjean  (supplier of updated owfs 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: Tue, 18 Dec 2018 20:48:32 +0100
Source: owfs
Binary: owfs-common owfs libow-3.2-3 libowcapi-3.2-3 libow-dev libownet-3.2-3 
libownet-dev owserver ow-shell ow-tools owfs-fuse owhttpd owftpd libow-php7 
libownet-php libow-perl libownet-perl python-ow python3-ow python-ownet 
python3-ownet libow-tcl owfs-doc
Architecture: all amd64 source
Version: 3.2p3+dfsg1-2
Distribution: unstable
Urgency: medium
Maintainer: Vincent Danjean 
Changed-By: Vincent Danjean 
Closes: 916559
Description: 
 libow-3.2-3 - 1-Wire File System full library
 libowcapi-3.2-3 - 1-Wire File System C library
 libow-dev  - 1-Wire File System (development files)
 libownet-3.2-3 - owserver protocol library
 libownet-dev - owserver protocol library (development files)
 libownet-perl - Perl module for accessing 1-wire networks
 libownet-php - Dallas 1-wire support: PHP OWNet library
 libow-perl - Dallas 1-wire support: Perl5 bindings
 libow-php7 - Dallas 1-wire support: PHP5 bindings
 libow-tcl  - Dallas 1-wire support: Tcl bindings
 owfs-common - common files used by any of the OWFS programs
 owfs   - Dallas 1-wire support
 owfs-doc   - Dallas 1-wire support: Documentation for owfs
 owfs-fuse  - 1-Wire filesystem
 owftpd - FTP daemon providing access to 1-Wire networks
 owhttpd- HTTP daemon providing access to 1-Wire networks
 owserver   - Backend server for 1-Wire control
 ow-shell   - shell utilities to talk to an 1-Wire owserver
 ow-tools   - tools to monitor or inspect a ow-server link
 python3-ow - Dallas 1-wire support: Python 3 bindings
 python3-ownet - Python 3 module for accessing 1-wire networks
 python-ow  - Dallas 1-wire support: Python 2 bindings
 python-ownet - Python 2 module for accessing 

Bug#915390: marked as done (clazy: Segmentation fault compiling any file)

[Debian Bug Tracking System]

Your message dated Tue, 18 Dec 2018 21:21:17 +
with message-id 
and subject line Bug#915390: fixed in clazy 1.4-4
has caused the Debian Bug report #915390,
regarding clazy: Segmentation fault compiling any file
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.)


-- 
915390: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915390
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: clazy
Version: 1.4-3
Severity: grave
Justification: renders package unusable

Dear Maintainer,

attempting to compile any file on my system results in a segfault.
Could it be that a runtime dependency is missing from d/control?

Steps to reproduce:

> touch a.cpp
> clazy a.cpp 
#0 0x7f825a95352a llvm::sys::PrintStackTrace(llvm::raw_ostream&) 
(/usr/lib/x86_64-linux-gnu/libLLVM-6.0.so.1+0x92152a)
#1 0x7f825a95164e llvm::sys::RunSignalHandlers() 
(/usr/lib/x86_64-linux-gnu/libLLVM-6.0.so.1+0x91f64e)
#2 0x7f825a9517dd (/usr/lib/x86_64-linux-gnu/libLLVM-6.0.so.1+0x91f7dd)
#3 0x7f825dc2b8e0 __restore_rt 
(/lib/x86_64-linux-gnu/libpthread.so.0+0x128e0)
#4 0x7f8254bc6ac4 (/usr/lib/x86_64-linux-gnu/libLLVM-7.so.1+0x106dac4)
#5 0x7f82543e9c78 
llvm::WebAssemblyTargetWasmStreamer::emitGlobalImport(llvm::StringRef) 
(/usr/lib/x86_64-linux-gnu/libLLVM-7.so.1+0x890c78)
#6 0x7f825dca90ca (/lib64/ld-linux-x86-64.so.2+0xf0ca)
#7 0x7f825dca91d6 (/lib64/ld-linux-x86-64.so.2+0xf1d6)
#8 0x7f825dcad253 (/lib64/ld-linux-x86-64.so.2+0x13253)
#9 0x7f8259a41adf _dl_catch_exception 
(/lib/x86_64-linux-gnu/libc.so.6+0x133adf)
#10 0x7f825dcacb1a (/lib64/ld-linux-x86-64.so.2+0x12b1a)
#11 0x7f82594a0276 __asprintf (/lib/x86_64-linux-gnu/libdl.so.2+0x1276)
#12 0x7f8259a41adf _dl_catch_exception 
(/lib/x86_64-linux-gnu/libc.so.6+0x133adf)
#13 0x7f8259a41b6f _dl_catch_error 
(/lib/x86_64-linux-gnu/libc.so.6+0x133b6f)
#14 0x7f82594a0975 (/lib/x86_64-linux-gnu/libdl.so.2+0x1975)
#15 0x7f82594a0331 dlopen (/lib/x86_64-linux-gnu/libdl.so.2+0x1331)
#16 0x7f825a93dc53 llvm::sys::DynamicLibrary::HandleSet::DLOpen(char 
const*, std::__cxx11::basic_string, 
std::allocator >*) (/usr/lib/x86_64-linux-gnu/libLLVM-6.0.so.1+0x90bc53)
#17 0x7f825a93def2 llvm::sys::DynamicLibrary::getPermanentLibrary(char 
const*, std::__cxx11::basic_string, 
std::allocator >*) (/usr/lib/x86_64-linux-gnu/libLLVM-6.0.so.1+0x90bef2)
#18 0x55d0d6d7daba 
clang::ExecuteCompilerInvocation(clang::CompilerInstance*) 
(/usr/lib/llvm-6.0/bin/clang+0x8e9aba)
#19 0x55d0d68d8678 cc1_main(llvm::ArrayRef, char const*, 
void*) (/usr/lib/llvm-6.0/bin/clang+0x444678)
#20 0x55d0d68c8117 main (/usr/lib/llvm-6.0/bin/clang+0x434117)
#21 0x7f8259930b17 __libc_start_main 
(/lib/x86_64-linux-gnu/libc.so.6+0x22b17)
#22 0x55d0d68d665a _start (/usr/lib/llvm-6.0/bin/clang+0x44265a)
Stack dump:
0.  Program arguments: /usr/lib/llvm-6.0/bin/clang -cc1 -triple 
x86_64-pc-linux-gnu -emit-obj -mrelax-all -disable-free -disable-llvm-verifier 
-discard-value-names -main-file-name a.cpp -mrelocation-model static 
-mthread-model posix -mdisable-fp-elim -fmath-errno -masm-verbose 
-mconstructor-aliases -munwind-tables -fuse-init-array -target-cpu x86-64 
-dwarf-column-info -debugger-tuning=gdb -resource-dir 
/usr/lib/llvm-6.0/lib/clang/6.0.1 -internal-isystem 
/usr/bin/../lib/gcc/x86_64-linux-gnu/8/../../../../include/c++/8 
-internal-isystem 
/usr/bin/../lib/gcc/x86_64-linux-gnu/8/../../../../include/x86_64-linux-gnu/c++/8
 -internal-isystem 
/usr/bin/../lib/gcc/x86_64-linux-gnu/8/../../../../include/x86_64-linux-gnu/c++/8
 -internal-isystem 
/usr/bin/../lib/gcc/x86_64-linux-gnu/8/../../../../include/c++/8/backward 
-internal-isystem /usr/include/clang/6.0.1/include/ -internal-isystem 
/usr/local/include -internal-isystem /usr/lib/llvm-6.0/lib/clang/6.0.1/include 
-internal-externc-isystem /usr/include/x86_64-linux-gnu 
-internal-externc-isystem /include -internal-externc-isystem /usr/include 
-fdeprecated-macro -fdebug-compilation-dir /home/alberto/tmp/biolim/build_clazy 
-ferror-limit 19 -fmessage-length 190 -fobjc-runtime=gcc -fcxx-exceptions 
-fexceptions -fdiagnostics-show-option -fcolor-diagnostics -load ClangLazy.so 
-add-plugin clang-lazy -o /tmp/a-239fc9.o -x c++ a.cpp 
clang: error: unable to execute command: Segmentation fault
clang: error: clang frontend command failed due to signal (use -v to see 
invocation)
clang version 6.0.1-9.2 (tags/RELEASE_601/final)
Target: x86_64-pc-linux-gnu
Thread model: posix
InstalledDir: /usr/bin
clang: note: diagnostic msg: PLEASE submit a bug report to 

Processed: retitle 916782 to harfbuzz fails to build on big endian

[Debian Bug Tracking System]

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

> retitle 916782 harfbuzz fails to build on big endian
Bug #916782 [src:harfbuzz] harfbuzz: fails to build on s390x and mips
Changed Bug title to 'harfbuzz fails to build on big endian' from 'harfbuzz: 
fails to build on s390x and mips'.
> thanks
Stopping processing here.

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

Bug#885638: GBonds Modernization

[Richard Laager]

I have a new version of the gbonds package prepared and sent to my
sponsor for upload.

The vast majority of the credit for this upload goes to Yavor Doganov
who submitted a series of patches to modernize the gbonds code, porting
it to GTK+ 3, GIO, and GSettings and restoring printing support! This
resolves the serious bugs which would have otherwise required the
removal of gbonds prior to the Buster release.

I am extremely grateful for this generous contribution of coding time
and skill!

Yavor Doganov: I made the following changes to your patches in the
process of accepting them:

Port to GTK+ 3 and GIO:
  - Dropped spurious diff header changes to other files
  - Folded in the remainder of debian/patches/libgnomeprint

^ These changes were cosmetic in nature.


Port to GSettings:
  - Install the schema and setting files into gbonds-data

^ These files were required. I simply added them to
  debian/gbonds-data.install so they ended up in the package.


I tested this with my usual real-world data file and usage. I also
tested downloading new redemption data from the Treasury. I tested the
printing functionality to the point of a Preview. It looks great to me!

-- 
Richard

Bug#911898: marked as done (firefox-esr: SIGSEGV on startup on ppc64el)

[Debian Bug Tracking System]

Your message dated Tue, 18 Dec 2018 20:39:55 +
with message-id 
and subject line Bug#911898: fixed in firefox-esr 60.4.0esr-1~deb9u1
has caused the Debian Bug report #911898,
regarding firefox-esr: SIGSEGV on startup on ppc64el
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.)


-- 
911898: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911898
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: firefox-esr
Version: 60.3.0esr-1~deb9u1
Severity: important

This is essentially a downstream bug report of bz#1477176 (
https://bugzilla.mozilla.org/show_bug.cgi?id=1477176 ).

firefox-esr currently segfaults right on startup on ppc64le during the first
memory allocation call.


I cannot provide a useful backtrace because firefox-esr-dbgsym is not available
(not even in stretch-proposed-updates, you should upload the package there)
since security doesn't have a dbgsym archive (#894081).


A workaround for this issue is to build firefox with (moz)jemalloc disabled. I'd
suggest to do this for any non-x86-based architecture like RHEL does, because
(moz)jemalloc doesn't seem to be too stable on exotic architectures.

Appending

%if DEB_HOST_ARCH != amd64 && DEB_HOST_ARCH != i386
ac_add_options --disable-jemalloc
%endif

to debian/browser.mozconfig.in just about does the trick.



Mihai



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: firefox-esr
Source-Version: 60.4.0esr-1~deb9u1

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

Debian distribution maintenance software
pp.
Mike Hommey  (supplier of updated firefox-esr 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, 12 Dec 2018 08:29:04 +0900
Source: firefox-esr
Binary: firefox-esr iceweasel firefox-esr-l10n-all iceweasel-l10n-all 
firefox-esr-l10n-ach iceweasel-l10n-ach firefox-esr-l10n-af iceweasel-l10n-af 
firefox-esr-l10n-an iceweasel-l10n-an firefox-esr-l10n-ar iceweasel-l10n-ar 
firefox-esr-l10n-as iceweasel-l10n-as firefox-esr-l10n-ast iceweasel-l10n-ast 
firefox-esr-l10n-az iceweasel-l10n-az firefox-esr-l10n-be iceweasel-l10n-be 
firefox-esr-l10n-bg iceweasel-l10n-bg firefox-esr-l10n-bn-bd 
iceweasel-l10n-bn-bd firefox-esr-l10n-bn-in iceweasel-l10n-bn-in 
firefox-esr-l10n-br iceweasel-l10n-br firefox-esr-l10n-bs iceweasel-l10n-bs 
firefox-esr-l10n-ca iceweasel-l10n-ca firefox-esr-l10n-cak iceweasel-l10n-cak 
firefox-esr-l10n-cs iceweasel-l10n-cs firefox-esr-l10n-cy iceweasel-l10n-cy 
firefox-esr-l10n-da iceweasel-l10n-da firefox-esr-l10n-de iceweasel-l10n-de 
firefox-esr-l10n-dsb iceweasel-l10n-dsb firefox-esr-l10n-el iceweasel-l10n-el 
firefox-esr-l10n-en-gb iceweasel-l10n-en-gb firefox-esr-l10n-en-za 
iceweasel-l10n-en-za
 firefox-esr-l10n-eo iceweasel-l10n-eo firefox-esr-l10n-es-ar 
iceweasel-l10n-es-ar firefox-esr-l10n-es-cl iceweasel-l10n-es-cl 
firefox-esr-l10n-es-es iceweasel-l10n-es-es firefox-esr-l10n-es-mx 
iceweasel-l10n-es-mx firefox-esr-l10n-et iceweasel-l10n-et firefox-esr-l10n-eu 
iceweasel-l10n-eu firefox-esr-l10n-fa iceweasel-l10n-fa firefox-esr-l10n-ff 
iceweasel-l10n-ff firefox-esr-l10n-fi iceweasel-l10n-fi firefox-esr-l10n-fr 
iceweasel-l10n-fr firefox-esr-l10n-fy-nl iceweasel-l10n-fy-nl 
firefox-esr-l10n-ga-ie iceweasel-l10n-ga-ie firefox-esr-l10n-gd 
iceweasel-l10n-gd firefox-esr-l10n-gl iceweasel-l10n-gl firefox-esr-l10n-gn 
iceweasel-l10n-gn firefox-esr-l10n-gu-in iceweasel-l10n-gu-in 
firefox-esr-l10n-he iceweasel-l10n-he firefox-esr-l10n-hi-in 
iceweasel-l10n-hi-in firefox-esr-l10n-hr iceweasel-l10n-hr firefox-esr-l10n-hsb 
iceweasel-l10n-hsb firefox-esr-l10n-hu iceweasel-l10n-hu firefox-esr-l10n-hy-am 
iceweasel-l10n-hy-am firefox-esr-l10n-ia iceweasel-l10n-ia
 firefox-esr-l10n-id iceweasel-l10n-id firefox-esr-l10n-is iceweasel-l10n-is 
firefox-esr-l10n-it iceweasel-l10n-it firefox-esr-l10n-ja iceweasel-l10n-ja 
firefox-esr-l10n-ka iceweasel-l10n-ka firefox-esr-l10n-kab iceweasel-l10n-kab 
firefox-esr-l10n-kk iceweasel-l10n-kk firefox-esr-l10n-km iceweasel-l10n-km 

Bug#916468: Conflict over /usr/bin/dune

[Philipp Kern]

Am 18.12.2018 um 18:48 schrieb Ian Jackson:
> But overall I think this, plus the history of the ocaml program's
> name, does demonstrate that the ocaml program's claim to the overall
> software name `dune', and the command name `dune' is incredibly weak.
> 
> I just checked and `odune' seems to be available.  For a build tool a
> reasonably short name is justified.  The `o' prefix is often used with
> ocaml and though there is of course a risk of clashes with both
> individual programs and with some suites like the old OpenStep stuff,
> it seems that `/usr/bin/odune', odune(1) et al, are not taken.

But then again it's a build tool that actually needs to be called its
name on the console (just like the node mess). whitedune is a GUI
program that could have any name as long as it's obvious from the
desktop metadata and in fact its webpage disappeared and it hasn't seen
a new upstream version since 2011. And the C++ library doesn't seem to
have a CLI name claim at all.

I suppose it's mostly the point that we package all free software on the
planet that we become an arbiter of names. But we should try not to be
that if we can avoid it.

Kind regards
Philipp Kern

Bug#906982: sysbench: FTBFS on armhf

[JCF Ploemen]

Meanwhile the package built successfully on ubuntu disco armhf, see
https://launchpad.net/ubuntu/+source/sysbench/1.0.15+ds-1/+build/15588300


pgpipBoYMe2h4.pgp
Description: OpenPGP digital signature

Processed: retitle 900912 to openjdk-11: Accessibility does not get loaded

[Debian Bug Tracking System]

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

> retitle 900912 openjdk-11: Accessibility does not get loaded
Bug #900912 [openjdk-11] openjdk-10: Accessibility does not get loaded
Changed Bug title to 'openjdk-11: Accessibility does not get loaded' from 
'openjdk-10: Accessibility does not get loaded'.
> thanks
Stopping processing here.

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

Bug#916683: libgnutls30: breaks msmtp 1.6.7-1

[Andreas Metzler]

On 2018-12-17 Jonas Smedegaard  wrote:
> Quoting Andreas Metzler (2018-12-17 19:37:05)
[msmtp / GnuTLS 3.6 breaks]
>> FWIW I have had successful connections against exim4 (gnutls 3.5 and 
>> 3.6). Which host are you trying to connect to?

> Sorry for exaggerating!

Not at all.

> The hosts I experienced problems with are mail.jones.dk and 
> mail.homebase.dk - both running Postfix on Debian stable (which made me 
> rule out them as cause for blame, but...) both of them managed by myself 
> with various attempts at tightening security, so I realize now that I 
> may possibly have exposed bugs in unusual setups rather than common 
> ones.

It might be the other way round, GnuTLS servers the only ones not
triggering the issue.

> Both systems are running in production so I am not happy doing drastic 
> experiments on them - but on the other hand they are public accessible 
> so available for testing this bug if needed.

Thanks! FWIW as a temporary workaround you can invoke msmtp with
--tls-priorities=NORMAL:-VERS-TLS1.3

cu Andreas

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

Bug#914435: marked as done (haskell-finite-field: Missing build-dependency on singletons)

[Debian Bug Tracking System]

Your message dated Tue, 18 Dec 2018 20:49:07 +0200
with message-id <20181218184907.dtc6lcenygtrx...@gmail.com>
and subject line Re: Bug#914435: haskell-finite-field: Missing build-dependency 
on singletons
has caused the Debian Bug report #914435,
regarding haskell-finite-field: Missing build-dependency on singletons
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.)


-- 
914435: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914435
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-finite-field
Version: 0.8.0
Severity: serious
Justification: fails to build from source

This package is not part of LTS. Do we want to continue maintaining it?
If so, we will have to package singletons.

-- 
Ilias
--- End Message ---
--- Begin Message ---
Version: haskell-finite-field/0.9.0-1

On Fri, Dec 07, 2018 at 07:58PM, Sean Whitton wrote:
> I've packaged it in DHG_packages.git.  I don't know if it will build yet
> but d/copyright is done, at least.

This package is needed by keysafe, so we should keep it.
haskell-singletons is now available on unstable, closing this bug.

Thanks,

-- 
Ilias--- End Message ---

Bug#916764: znc-backlog: overly strict dependency on znc?

[Andreas Beckmann]

On 2018-12-18 18:13, Felipe Sateler wrote:
> Hi,
> On Tue, Dec 18, 2018 at 8:33 AM Andreas Beckmann  wrote:
> 
>> Package: znc-backlog
>> Version: 0.20170713-1
>> Severity: serious
>>
> 
> Hmm, not sure this is warranted.

It's currently uninstallable in sid.
Instead of requesting a binNMU (and doing so everytime znc changes), I
asked this question here.

>> do you really need a dependency on the exact binary version of znc
>> available at the build time of znc-backlog? I.e., every time znc
>> gets uploaded *or binNMUed*, a binNMU of znc-backlog is needed, too.
>> Wouldn't a dependency computed from the upstream version be sufficient?
>> E.g. znc (>= ${znc:upstreamversion}), znc (<< ${znc:upstreamversion}+)
>>
>>
> I'm using the same as the znc plugins shipped by znc itself. AFAIK, the znc
> ABI is not stable, so backporting an upstream patch could potentially break
> other plugins.

But that's unlikely to happen on binNMUs, isn't it?

> Perhaps znc could Provide: znc-plugin-$somenumber, which could be used by
> out-of-tree plugins? Adding the znc maintainers to the loop for their input

That's being used successfully by some packages ...


Andreas

Bug#916800: phybin: FTBFS with newer GHC

[Ilias Tsitsimpis]

Package: phybin
Version: 0.3-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Dear maintainer,

phybin FTBFS with newer versions of GHC (>= 8.4) with the following error:

[1 of 9] Compiling Bio.Phylogeny.PhyBin.CoreTypes ( 
Bio/Phylogeny/PhyBin/CoreTypes.hs, 
dist-ghc/build/test-phybin/test-phybin-tmp/Bio/Phylogeny/PhyBin/CoreTypes.o )

Bio/Phylogeny/PhyBin/CoreTypes.hs:112:35: error:
Ambiguous occurrence `<>'
It could refer to either `Prelude.<>',
 imported from 
`Prelude' at Bio/Phylogeny/PhyBin/CoreTypes.hs:7:8-37
 (and 
originally defined in `GHC.Base')
  or 
`Text.PrettyPrint.HughesPJClass.<>',
 imported from 
`Text.PrettyPrint.HughesPJClass' at Bio/Phylogeny/PhyBin/CoreTypes.hs:40:1-58
 (and 
originally defined in `pretty-1.1.3.6:Text.PrettyPrint.HughesPJ')
|
112 | displayDefaultTree orig = loop tr <> ";"
|   ^^

Bio/Phylogeny/PhyBin/CoreTypes.hs:120:27: error:
Ambiguous occurrence `<>'
It could refer to either `Prelude.<>',
 imported from 
`Prelude' at Bio/Phylogeny/PhyBin/CoreTypes.hs:7:8-37
 (and 
originally defined in `GHC.Base')
  or 
`Text.PrettyPrint.HughesPJClass.<>',
 imported from 
`Text.PrettyPrint.HughesPJClass' at Bio/Phylogeny/PhyBin/CoreTypes.hs:40:1-58
 (and 
originally defined in `pretty-1.1.3.6:Text.PrettyPrint.HughesPJ')
|
120 |  Just val -> base <> text ":[" <> text (show val) <> text 
"]"
|   ^^

Bio/Phylogeny/PhyBin/CoreTypes.hs:120:40: error:
Ambiguous occurrence `<>'
It could refer to either `Prelude.<>',
 imported from 
`Prelude' at Bio/Phylogeny/PhyBin/CoreTypes.hs:7:8-37
 (and 
originally defined in `GHC.Base')
  or 
`Text.PrettyPrint.HughesPJClass.<>',
 imported from 
`Text.PrettyPrint.HughesPJClass' at Bio/Phylogeny/PhyBin/CoreTypes.hs:40:1-58
 (and 
originally defined in `pretty-1.1.3.6:Text.PrettyPrint.HughesPJ')
|
120 |  Just val -> base <> text ":[" <> text (show val) <> text 
"]"
|^^

Bio/Phylogeny/PhyBin/CoreTypes.hs:120:59: error:
Ambiguous occurrence `<>'
It could refer to either `Prelude.<>',
 imported from 
`Prelude' at Bio/Phylogeny/PhyBin/CoreTypes.hs:7:8-37
 (and 
originally defined in `GHC.Base')
  or 
`Text.PrettyPrint.HughesPJClass.<>',
 imported from 
`Text.PrettyPrint.HughesPJClass' at Bio/Phylogeny/PhyBin/CoreTypes.hs:40:1-58
 (and 
originally defined in `pretty-1.1.3.6:Text.PrettyPrint.HughesPJ')
|
120 |  Just val -> base <> text ":[" <> text (show val) <> text 
"]"
|   ^^

Bio/Phylogeny/PhyBin/CoreTypes.hs:121:47: error:
Ambiguous occurrence `<>'
It could refer to either `Prelude.<>',
 imported from 
`Prelude' at Bio/Phylogeny/PhyBin/CoreTypes.hs:7:8-37
 (and 
originally defined in `GHC.Base')
  or 
`Text.PrettyPrint.HughesPJClass.<>',
 imported from 
`Text.PrettyPrint.HughesPJClass' at Bio/Phylogeny/PhyBin/CoreTypes.hs:40:1-58
 (and 
originally defined in `pretty-1.1.3.6:Text.PrettyPrint.HughesPJ')
|
121 |   

Processed: dpkg: update-alternatives does not properly deregister obsolete slaves if the link group is currently broken

[Debian Bug Tracking System]

Processing control commands:

> found -1 1.18.25
Bug #916799 [dpkg] dpkg: update-alternatives does not properly deregister 
obsolete slaves if the link group is currently broken
Marked as found in versions dpkg/1.18.25.

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

Bug#916799: dpkg: update-alternatives does not properly deregister obsolete slaves if the link group is currently broken

[Andreas Beckmann]

Package: dpkg
Version: 1.19.2
Severity: serious
Control: found -1 1.18.25

Hi,

there is a problem with update-alternatives not properly deregistering
obsolete slaves:

==
#!/bin/sh

update-alternatives --version
update-alternatives --remove-all foobar

set -x
touch /foo /foo.1
touch /bar /bar.1
update-alternatives --display foobar
update-alternatives --install /foobar foobar /foo 23 --slave /foobar.1 foobar-1 
/foo.1 --slave /barfoo barfoo /bar --slave /barfoo.1 barfoo-1 /bar.1
update-alternatives --display foobar
rm /bar /bar.1
update-alternatives --install /foobar foobar /foo 42 --slave /foobar.1 foobar-1 
/foo.1
update-alternatives --display foobar
update-alternatives --install /foobar foobar /foo 42 --slave /foobar.1 foobar-1 
/foo.1
update-alternatives --display foobar
==

# ./foobar.sh 
Debian update-alternatives version 1.18.25.

This is free software; see the GNU General Public License version 2 or
later for copying conditions. There is NO warranty.
update-alternatives: error: no alternatives for foobar
+ touch /foo /foo.1
+ touch /bar /bar.1
+ update-alternatives --display foobar
update-alternatives: error: no alternatives for foobar
+ update-alternatives --install /foobar foobar /foo 23 --slave /foobar.1 
foobar-1 /foo.1 --slave /barfoo barfoo /bar --slave /barfoo.1 barfoo-1 /bar.1
update-alternatives: using /foo to provide /foobar (foobar) in auto mode
+ update-alternatives --display foobar
foobar - auto mode
  link best version is /foo
  link currently points to /foo
  link foobar is /foobar
  slave barfoo is /barfoo
  slave barfoo-1 is /barfoo.1
  slave foobar-1 is /foobar.1
/foo - priority 23
  slave barfoo: /bar
  slave barfoo-1: /bar.1
  slave foobar-1: /foo.1
+ rm /bar /bar.1
+ update-alternatives --install /foobar foobar /foo 42 --slave /foobar.1 
foobar-1 /foo.1
update-alternatives: warning: forcing reinstallation of alternative /foo 
because link group foobar is broken
+ update-alternatives --display foobar
foobar - auto mode
  link best version is /foo
  link currently points to /foo
  link foobar is /foobar
  slave barfoo-1 is /barfoo.1
  slave foobar-1 is /foobar.1
*** *** *** at this point there should not be any barfoo slaves left *** *** ***
/foo - priority 42
  slave foobar-1: /foo.1
+ update-alternatives --install /foobar foobar /foo 42 --slave /foobar.1 
foobar-1 /foo.1
+ update-alternatives --display foobar
foobar - auto mode
  link best version is /foo
  link currently points to /foo
  link foobar is /foobar
  slave foobar-1 is /foobar.1
/foo - priority 42
  slave foobar-1: /foo.1

# sh foobar.sh 
Debian update-alternatives version 1.17.27.

This is free software; see the GNU General Public License version 2 or
later for copying conditions. There is NO warranty.
update-alternatives: error: no alternatives for foobar
+ touch /foo /foo.1
+ touch /bar /bar.1
+ update-alternatives --display foobar
update-alternatives: error: no alternatives for foobar
+ update-alternatives --install /foobar foobar /foo 23 --slave /foobar.1 
foobar-1 /foo.1 --slave /barfoo barfoo /bar --slave /barfoo.1 barfoo-1 /bar.1
update-alternatives: using /foo to provide /foobar (foobar) in auto mode
+ update-alternatives --display foobar
foobar - auto mode
  link currently points to /foo
/foo - priority 23
  slave barfoo: /bar
  slave barfoo-1: /bar.1
  slave foobar-1: /foo.1
Current 'best' version is '/foo'.
+ rm /bar /bar.1
+ update-alternatives --install /foobar foobar /foo 42 --slave /foobar.1 
foobar-1 /foo.1
update-alternatives: warning: forcing reinstallation of alternative /foo 
because link group foobar is broken
+ update-alternatives --display foobar
foobar - auto mode
  link currently points to /foo
/foo - priority 42
  slave foobar-1: /foo.1
Current 'best' version is '/foo'.
+ update-alternatives --install /foobar foobar /foo 42 --slave /foobar.1 
foobar-1 /foo.1
+ update-alternatives --display foobar
foobar - auto mode
  link currently points to /foo
/foo - priority 42
  slave foobar-1: /foo.1
Current 'best' version is '/foo'.

So this is reproducible in stretch, too, but not in jessie.

The change of priority is not even needed.

The problem does not occur if there is only a single broken slave to be
removed.


The slaves to be removed don't even need to be broken ...

# update-alternatives --install /test test /bin 1 --slave /one one /bin --slave 
/two two /bin --slave /three three /bin
# update-alternatives --install /test test /bin 1
# update-alternatives --install /test2 test2 /bin 1 --slave /one one /bin 
--slave /two two /bin --slave /three three /bin
update-alternatives: error: alternative three can't be slave of test2: it is a 
slave of test
# update-alternatives --display test
test - auto mode
  link best version is /bin
  link currently points to /bin
  link test is /test
  slave three is /three
/bin - priority 1

This didn't work with only two slaves being removed ...


Also the "forcing reinstallation of alternative ..." message is confusing
at this situation, as 

Bug#916468: Conflict over /usr/bin/dune

[Andrey Rahmatullin]

Even firefox was renamed twice.

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Bug#916468: Conflict over /usr/bin/dune

[Ian Jackson]

Ian Jackson writes ("Re: Conflict over /usr/bin/dune"):
>  https://www.google.com/search?q=dune+software
>  https://en.wikipedia.org/wiki/Dune_(software)
>  https://www.google.com/search?q=%2Fusr%2Fbin%2Fdune
> 
> Under the circumstances it seems obvious that, at the very least, the
> ocaml build tool should not be allowed the name /usr/bin/dune.

Perhaps I should have stated this explicitly, since it was not obvious
unless you follow the links.

`Dune' is not, as a piece of software, primarily either the ocaml
build tool, or the 3D modeller.

Mostly it is DUNE, a "modular C++ library for the solution of partial
differential equations using grid-based methods".  That's what you get
if you visit the Wikipedia link I provided - not even a disambiguation
link.  The others don't rate a mention.

It is already in Debian:

stretch$ apt-file search /usr/bin/dune
libdune-common-dev: /usr/bin/dune-am2cmake
libdune-common-dev: /usr/bin/dune-ctest
libdune-common-dev: /usr/bin/dune-git-whitespace-hook
libdune-common-dev: /usr/bin/dune-remove-autotools
libdune-common-dev: /usr/bin/dunecontrol
libdune-common-dev: /usr/bin/duneproject
whitedune: /usr/bin/dune
stretch$

Now of course libdune-common-dev only has various /usr/bin/dune?*
so doesn't precisely conflict with this.  It would be possible for
one of whitedune and ocaml-dune (`odune?') to have /usr/bin/dune
to coexist with it.

But overall I think this, plus the history of the ocaml program's
name, does demonstrate that the ocaml program's claim to the overall
software name `dune', and the command name `dune' is incredibly weak.

I just checked and `odune' seems to be available.  For a build tool a
reasonably short name is justified.  The `o' prefix is often used with
ocaml and though there is of course a risk of clashes with both
individual programs and with some suites like the old OpenStep stuff,
it seems that `/usr/bin/odune', odune(1) et al, are not taken.

HTH.  I know this may just be seen as my usual opinion in these
Judgement of Solomon cases and that the underlying policy is
controversial.  But whenever something like this happens and causes a
major stink, it serves to demonstrate to others what they want to, and
can, avoid.

Ian.

-- 
Ian JacksonThese opinions are my own.

If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.

Bug#915050: (gitlab) Re: Bug#915050: Keep out of testing

[Pirate Praveen]

On 12/18/18 8:41 PM, Holger Levsen wrote:
> On Tue, Dec 18, 2018 at 08:38:39PM +0530, Pirate Praveen wrote:
>> But if that is not possible, volatile as a separate archive is also fine. 
> 
> instead of volatile we need PPAs.

I think a redefined volatile is the best option for sharing work. But
PPA approach is best in case of conflicts.

I'm leaning towards volatile and hence I proposed it. If you feel
strongly about PPAs, please propose and drive it. Either option will
work for me.



signature.asc
Description: OpenPGP digital signature

Bug#915050: (gitlab) Re: Bug#915050: Keep out of testing

[Jeremy Bicha]

On Tue, Dec 18, 2018 at 10:12 AM Holger Levsen  wrote:
> On Tue, Dec 18, 2018 at 08:38:39PM +0530, Pirate Praveen wrote:
> > But if that is not possible, volatile as a separate archive is also fine.
>
> instead of volatile we need PPAs.

Shortly before the Stretch release, when I was scrambling to find a
way to provide updates for webkit2gtk for Stretch's lifetime, I think
volatile was suggested as something that was able to sort of do what I
needed.

But it's not a good example since Debian Security ought to handle
webkit2gtk updates for Buster, as is done with Firefox ESR and
Chromium.

Thanks,
Jeremy Bicha

Processed: limit source to linux, tagging 916774

[Debian Bug Tracking System]

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

> limit source linux
Limiting to bugs with field 'source' containing at least one of 'linux'
Limit currently set to 'source':'linux'

> tags 916774 + pending
Bug #916774 [linux-perf-4.19] linux-perf metapackage fails to upgrade due to 
file conflict between linux-perf-4.18 & linux-perf-4.19
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#916468: Conflict over /usr/bin/dune

[Ian Jackson]

Resending because
  1. mailing @packages.d.o rather than @packages.qa.d.o
  2. fixed one of the google urls which I broke while
 removing tracking crap

Stéphane Glondu writes ("Conflict over /usr/bin/dune"):
> The "dune" package (of which I am the maintainer) is a popular build
> system for OCaml projects. It is pretty recent, has strong upstream
> support, and more and more projects are switching to it, which is a
> reason to have it in Debian.
> 
> It was previously named jbuilder, but has been renamed due to a conflict
> with another software. Upstream is reluctant to rename it again.

This seems quite a striking pair of errors.  `jbuilder' ?  What were
they thinking ?  I know language-specific communities can be a bit
insular but `jbuilder' is obviously absurd for an ocaml build tool.

And then having got into that pickle, what on earth possessed them to
pick the name `dune' ?  Did they learn at all from their mistake and
think about this at all ?  Do even the briefest of checks ?  Even if
they couldn't be bothered to do a Debian file search,

 https://www.google.com/search?q=dune+software
 https://en.wikipedia.org/wiki/Dune_(software)
 https://www.google.com/search?q=%2Fusr%2Fbin%2Fdune

Under the circumstances it seems obvious that, at the very least, the
ocaml build tool should not be allowed the name /usr/bin/dune.

Ian.

-- 
Ian JacksonThese opinions are my own.

If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.

Bug#916764: znc-backlog: overly strict dependency on znc?

[Felipe Sateler]

Hi,
On Tue, Dec 18, 2018 at 8:33 AM Andreas Beckmann  wrote:

> Package: znc-backlog
> Version: 0.20170713-1
> Severity: serious
>

Hmm, not sure this is warranted.


> User: debian...@lists.debian.org
> Usertags: piuparts
>
> Hi,
>
> do you really need a dependency on the exact binary version of znc
> available at the build time of znc-backlog? I.e., every time znc
> gets uploaded *or binNMUed*, a binNMU of znc-backlog is needed, too.
> Wouldn't a dependency computed from the upstream version be sufficient?
> E.g. znc (>= ${znc:upstreamversion}), znc (<< ${znc:upstreamversion}+)
>
>
I'm using the same as the znc plugins shipped by znc itself. AFAIK, the znc
ABI is not stable, so backporting an upstream patch could potentially break
other plugins.

Perhaps znc could Provide: znc-plugin-$somenumber, which could be used by
out-of-tree plugins? Adding the znc maintainers to the loop for their input


-- 

Saludos,
Felipe Sateler

Bug#916468: Conflict over /usr/bin/dune

[Ian Jackson]

Stéphane Glondu writes ("Conflict over /usr/bin/dune"):
> The "dune" package (of which I am the maintainer) is a popular build
> system for OCaml projects. It is pretty recent, has strong upstream
> support, and more and more projects are switching to it, which is a
> reason to have it in Debian.
> 
> It was previously named jbuilder, but has been renamed due to a conflict
> with another software. Upstream is reluctant to rename it again.

This seems ... quite a striking error.

What on earth possessed them to pick the name `dune' ?  Even if they
couldn't be bothered to do a Debian file search,

 https://www.google.com/search?q=dune+software
 https://en.wikipedia.org/wiki/Dune_(software)
 https://www.google.com/search?q=%2Fusr%2Fbin%2Fdune

Under the circumstances it seems obvious that no-one should be allowed
the name /usr/bin/dune.

Ian.

-- 
Ian JacksonThese opinions are my own.

If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.

Bug#916774: linux-perf metapackage fails to upgrade due to file conflict between linux-perf-4.18 & linux-perf-4.19

[Ben Hutchings]

On Tue, 2018-12-18 at 21:24 +0800, Paul Wise wrote:
> Package: linux-perf-4.19
> Version: 4.19.9-1
> Severity: serious
> 
> I had the linux-perf metapackage fail to upgrade due to a file conflict
> between linux-perf-4.18 & linux-perf-4.19:
[...]
> dpkg: error processing archive 
> /var/cache/apt/archives/linux-perf-4.19_4.19.9-1_amd64.deb (--unpack):
>  trying to overwrite '/usr/lib/perf/examples/bpf/5sec.c', which is also in 
> package linux-perf-4.18 4.18.20-2
[...]

The linux-perf-* packages are intended to be coinstallable (though in
practice libperl sometimes prevents that).

We have a build-time test that all installed file paths are versioned:

! find $(DESTDIR) -name '*perf*' \! -path '*[_-]$(VERSION)*' | grep  .

but now I see that that doesn't work because -path matches against the
full path, which includes $(DESTDIR), which includes $(VERSION).

Ben.

-- 
Ben Hutchings
Anthony's Law of Force: Don't force it, get a larger hammer.



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

Processed: found 909922 in 8.4.4+dfsg1-1, found 905532 in 0.1.67-1.1, found 905516 in 15 ...

[Debian Bug Tracking System]

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

> found 909922 8.4.4+dfsg1-1
Bug #909922 [ghc-doc] ghc-doc: unowned files after purge (policy 6.8, 10.8): 
/usr/share/doc/ghc-doc/html/libraries/{haddock-bundle.min.js,quick-jump.css}
Marked as found in versions ghc/8.4.4+dfsg1-1.
> found 905532 0.1.67-1.1
Bug #905532 [ivulncheck-web] ivulncheck-web: unowned files after purge (policy 
6.8, 10.8): /etc/ivulncheck/htpasswd_web
Marked as found in versions ivulncheck/0.1.67-1.1.
> found 905516 15
Bug #905516 [openstack-cluster-installer-poc] openstack-cluster-installer-poc: 
unowned directories after purge: 
/var/lib/openstack-cluster-installer-poc/{runtime,templates}/
Marked as found in versions openstack-cluster-installer/15.
> found 905282 python-lldb-7/1:7.0.1-1
Bug #905282 [python-lldb-6.0] python-lldb-6.0: broken symlinks: 
/usr/lib/llvm-6.0/lib/python2.7/site-packages/lldb/*
The source python-lldb-7 and version 1:7.0.1-1 do not appear to match any 
binary packages
Marked as found in versions python-lldb-7/1:7.0.1-1.
> found 857653 liblld-7/1:7.0.1-1
Bug #857653 [liblld-6.0] liblld-4.0: missing liblld-4.0.so.1
The source liblld-7 and version 1:7.0.1-1 do not appear to match any binary 
packages
Marked as found in versions liblld-7/1:7.0.1-1.
> found 857680 llvm-7-examples/1:7.0.1-1
Bug #857680 [llvm-6.0-examples] llvm-3.8-examples: broken symlinks: 
/usr/share/doc/llvm-3.8-examples/Makefile.* -> 
../../../lib/llvm-3.8/build/Makefile.*
The source llvm-7-examples and version 1:7.0.1-1 do not appear to match any 
binary packages
Marked as found in versions llvm-7-examples/1:7.0.1-1.
> found 821118 5.6.0+dfsg1-4
Bug #821118 [libactivemq-java] libactivemq-java - Missing maven dependencies
Marked as found in versions activemq/5.6.0+dfsg1-4.
> found 915870 gccgo-doc/5:7.2.0-2
Bug #915870 [gccgo-doc] gccgo-doc: broken symlinks: 
/usr/share/man/man1/gccgo.1.gz, /usr/share/info/gccgo.info.gz
The source gccgo-doc and version 5:7.2.0-2 do not appear to match any binary 
packages
Marked as found in versions gccgo-doc/5:7.2.0-2.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
821118: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821118
857653: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857653
857680: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857680
905282: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905282
905516: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905516
905532: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905532
909922: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909922
915870: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915870
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#915050: (gitlab) Re: Bug#915050: Keep out of testing

[Holger Levsen]

On Tue, Dec 18, 2018 at 08:38:39PM +0530, Pirate Praveen wrote:
> But if that is not possible, volatile as a separate archive is also fine. 

instead of volatile we need PPAs.


-- 
cheers,
Holger

---
   holger@(debian|reproducible-builds|layer-acht).org
   PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C


signature.asc
Description: PGP signature

Bug#915050: (gitlab) Re: Bug#915050: Keep out of testing

[Pirate Praveen]

On 2018, ഡിസംബർ 18 7:14:14 PM IST, Rhonda D'Vine  wrote:
> And yes, I'm with Alexander, the volatile maintenance can't be dumped
>on the backports team.  It's a different workflow anyway.

My proposal for backports is to have only the dependencies of packages in 
volatile that fall in the current definition of backports kept there, ie,

1. They are already in testing and
2. will be part of next stable.

And use volatile only for packages that cannot fit this criteria. I'd be happy 
to join the backports team to help with the extra load. I hope others will join 
too.

But if that is not possible, volatile as a separate archive is also fine. It is 
just that many packages will have to be in both archives and that is a lot of 
extra work, which I think can be avoided.
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Bug#916782: harfbuzz: fails to build on s390x and mips

[Julien Cristau]

On Tue, Dec 18, 2018 at 09:42:55AM -0500, Jeremy Bicha wrote:
> Source: harfbuzz
> Version: 2.2.0-1
> Severity: serious
> Tags: ftbfs
> 
> harfbuzz fails to build on the release architectures s390x and mips.
> The new version fails to build on several non-release architectures
> too.
> 
> https://buildd.debian.org/status/package.php?p=harfbuzz
> 
Specifically it seems to fail tests on all big-endian archs.

Cheers,
Julien

Bug#916782: harfbuzz: fails to build on s390x and mips

[Jeremy Bicha]

Source: harfbuzz
Version: 2.2.0-1
Severity: serious
Tags: ftbfs

harfbuzz fails to build on the release architectures s390x and mips.
The new version fails to build on several non-release architectures
too.

https://buildd.debian.org/status/package.php?p=harfbuzz

Thanks,
Jeremy Bicha

Bug#916781: slack-desktop: Segmentation fault

[Eric Taylor]

Package: slack-desktop
Version: 3.3.3
Severity: grave
Justification: renders package unusable

Dear Maintainer,

   When trying to run slack I recive a segmentation fault.
   It seems to be related to libnode. I ran valgrind slack and get:
==14607== Process terminating with default action of signal 11 (SIGSEGV)
==14607==  Bad permissions for mapped region at address 0xDBF060
==14607==at 0xDBF060: ??? (in /usr/lib/slack/slack)
==14607==by 0x710F071: 
node::http2::Http2Session::Callbacks::Callbacks(bool) (in 
/usr/lib/slack/libnode.so)
==14607==by 0x710F134: ??? (in /usr/lib/slack/libnode.so)
==14607==by 0x5853399: call_init.part.0 (dl-init.c:72)
==14607==by 0x5853495: call_init (dl-init.c:118)
==14607==by 0x5853495: _dl_init (dl-init.c:119)
==14607==by 0x58450C9: ??? (in /lib/x86_64-linux-gnu/ld-2.28.so)




-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing'), (2, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.18.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages slack-desktop depends on:
pn  apt-transport-https  
ii  gconf-service3.2.6-5
ii  gconf2   3.2.6-5
ii  gvfs-bin 1.38.1-1
ii  libappindicator1 0.4.92-7
ii  libcurl4 7.62.0-1
ii  libgcrypt20  1.8.4-4
ii  libgtk2.0-0  2.24.32-3
ii  libnotify4   0.7.7-3
ii  libnss3  2:3.41-1
ii  libsecret-1-00.18.6-3
ii  libudev1 239-15
ii  libxss1  1:1.2.3-1
ii  libxtst6 2:1.2.3-1
ii  python   2.7.15-3
ii  xdg-utils1.1.3-1

slack-desktop recommends no packages.

slack-desktop suggests no packages.

-- debconf-show failed

Bug#916778: cylc: FTBFS when built with dpkg-buildpackage -A

[Santiago Vila]

Package: src:cylc
Version: 7.8.0-3
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster with dpkg-buildpackage -A but it failed:


[...]
dh  binary-indep --with python2
   dh_testroot -i
   dh_prep -i
   dh_installdirs -i
   debian/rules override_dh_auto_install
make[1]: Entering directory '/<>'
# Don't support gpanel. Requires gnome2's gnomeapplet.
rm -rf  bin/cylc-gpanel conf/gpanel
mkdir -p debian/tmp/usr/bin
mkdir -p debian/tmp/etc/cylc/gcylcrc
cp bin/cylc debian/tmp/usr//bin/cylc
cp etc/gcylc.rc.eg debian/tmp/etc/cylc/gcylcrc/gcylc.rc
cp etc/global-tests.rc.eg debian/tmp/etc/cylc/gcylcrc/global-tests.rx
cp etc/gcylc-themes.rc debian/tmp/etc/cylc/gcylcrc
find . -name '*.t' -exec chmod +x {} \;
find . -name test_header -exec chmod +x {} \;
chmod +x bin/*
install -d -m 0755 
/<>/debian/cylc-el/usr/share/emacs/site-lisp/cylc
install-m 0644 etc/syntax/cylc-mode.el \
   
/<>/debian/cylc-el/usr/share/emacs/site-lisp/cylc/cylc-mode.el
# Do this part if full build (not just arch-dependent)
make[1]: Leaving directory '/<>'
   dh_install -i
   dh_installdocs -i
   dh_installchangelogs -i
   dh_installexamples -i
dh_installexamples: Cannot find (any matches for) "examples/*" (tried in .)

   dh_python2 -i
E: dh_python2 dh_python2:408: no package to act on (python-foo or one with 
${python:Depends} in Depends)
   dh_perl -i
   dh_link -i
   dh_strip_nondeterminism -i
   dh_compress -i
   debian/rules override_dh_fixperms
make[1]: Entering directory '/<>'
# Delete after install. Use packages instead.
for p in Pyro cherrypy markupsafe jinja2 ; do \
rm -rf debian/python-cylc/usr/lib/python2.7/dist-packages/$p ; \
done
# shipped separately
find debian/python-cylc -name glyphicons-halflings-regular.ttf -delete
find: 'debian/python-cylc': No such file or directory
make[1]: *** [debian/rules:38: override_dh_fixperms] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:5: binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


The usual recipe is to split override_dh_foo into override_dh_foo-arch
and override_dh_foo-indep, but in this case it seems a little bit strange
that you are deleting things in the fixperms target (which is usually
for fixing perms).

Also, please consider uploading in source-only form (dpkg-buildpackage -S)
so that this kind of bugs do not propagate to testing and we have official
build logs for the arch:all autobuilder, currently missing here:

https://buildd.debian.org/status/package.php?p=cylc

Thanks.

Bug#916375: apache2: Segmentation fault when mod_perl.so is loaded

[Hans-Georg Thien]

Thanks Niko,

it seems that you where right regarding libmariadbclient18 ...

downgrading libmariadbclient18 fixed the issue :-)

    dpkg -i libmariadbclient18_10.1.26-0+deb9u1_amd64.deb



Niko Tyni wrote:

On Thu, Dec 13, 2018 at 06:44:32PM +0100, h.thien wrote:

Package: apache2
Version: 2.4.25-3+deb9u6
Severity: grave
Tags: patch
Justification: renders package unusable
gdb> Thread 1 "/opt/otrs/bin/cgi-bi" received signal SIGSEGV, 
Segmentation fault.
gdb> bt
#0  0x7fffdcd290c7 in free_defaults () from 
/usr/lib/x86_64-linux-gnu/libmariadbclient.so.18
We are using unattended upgrades (security only), and we suspect that 
an automatic system update has installed a new Perl version that now causes 
these problems.

Have you ruled out the MariaDB update? That one seems the most
likely to have triggered this regression.

   https://www.debian.org/security/2018/dsa-4341

(Not sure how reliably you got the list of loaded shared libraries;
you seem to be running the prefork mpm so presumably only some of your
apache processes will have the libraries loaded by the actual Perl
application.)




--
Hans-Georg Thien | Software Engineer
callas software GmbH | Schoenhauser Allee 6/7 | 10119 Berlin | Germany
Tel +49.30.4439031-0 | Fax +49.30.4416402 | www.callassoftware.com
Amtsgericht Charlottenburg, HRB 59615
Geschäftsführung: Olaf Drümmer, Ulrich Frotscher, Dietrich von Seggern

Bug#915050: (gitlab) Re: Bug#915050: Keep out of testing

[Rhonda D'Vine]

Hey,

* Pirate Praveen  [2018-12-18 09:34:46 CET]:
> On 12/3/18 8:11 PM, Dominik George wrote:
> >> well, Debian is using gitlab!!! so this sentence has no sense. The
> >> problem here
> >> is that is a complex software that depends of a lot of pieces and it's
> >> not
> >> easy/possible to fit the definition. So, maybe we should create another
> >> category
> >> of software.
> > 
> > Yes, and that Debian officially uses GitLab, from a foreign source, without 
> > being able to support it in Debian, does make me feel ashamed for the 
> > project.
> > 
> >> maybe creating another kind of repo. debian-contributuions
> >> debian-blabla, whatever.
> >>
> > 
> > We had volatile, which, redefined properly, could help. I am trying to 
> > draft such a definition.
> 
> Did you get a chance to work on it?

 Yes, it looks very much that the shutting down of volatile made wishes
appear for backports to cover it - while it wasn't (and shouldn't) be
the scope for it.  It would make it indistinguishable which packages
within backports are following the regular rules and which would be
those fast moving targets without any useful tracking or upgrade
features in the regular sense.

 (Part of that was btw. also the creation of a seperate sloppy pocket
for backports from oldstable+2 releases, to make it clear what to expect
in there)

 And yes, I'm with Alexander, the volatile maintenance can't be dumped
on the backports team.  It's a different workflow anyway.

 Good luck,
Rhonda
-- 
Fühlst du dich mutlos, fass endlich Mut, los  |
Fühlst du dich hilflos, geh raus und hilf, los| Wir sind Helden
Fühlst du dich machtlos, geh raus und mach, los   | 23.55: Alles auf Anfang
Fühlst du dich haltlos, such Halt und lass los|

Bug#912121: marked as done (bsd-finger misses the generator for configure)

[Debian Bug Tracking System]

Your message dated Tue, 18 Dec 2018 13:49:34 +
with message-id 
and subject line Bug#912121: fixed in bsd-finger 0.17-15.2
has caused the Debian Bug report #912121,
regarding bsd-finger misses the generator for configure
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.)


-- 
912121: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912121
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: netkit-ntalk
Version: 0.17-15
Severity: serious
Justification: DFSG #2
User: helm...@debian.org
Usertags: rebootstrap

The configure file in the netkit-ntalk is generated using confgen from
MCONFIG.in. However, the generator is missing. No package in unstable
contains said confgen tool. Thus configure cannot be regenerated after
fixing a bug. That's a violation of DFSG #2.

Helmut
--- End Message ---
--- Begin Message ---
Source: bsd-finger
Source-Version: 0.17-15.2

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

Debian distribution maintenance software
pp.
Christoph Biedl  (supplier of updated 
bsd-finger package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 08 Dec 2018 10:36:30 +0100
Source: bsd-finger
Binary: finger fingerd
Architecture: source
Version: 0.17-15.2
Distribution: unstable
Urgency: medium
Maintainer: Anibal Monsalve Salazar 
Changed-By: Christoph Biedl 
Description:
 finger - user information lookup program
 fingerd- remote user information server
Closes: 873085 912121
Changes:
 bsd-finger (0.17-15.2) unstable; urgency=medium
 .
   * Non-maintainer upload
   * Use cmake as build system. Closes: #873085, #912121
Checksums-Sha1:
 6b3d3062af7e3eed62f462dd55a0c8d5441c4a63 1767 bsd-finger_0.17-15.2.dsc
 417e00a4b004d4a14fc65d78bda642f1cbb8effc 0 
bsd-finger_0.17-15.2.debian.tar.bz2
 d6a82691d91c763045e594fd945bfa99caa1b150 6824 
bsd-finger_0.17-15.2_powerpc.buildinfo
Checksums-Sha256:
 5b2d894d8e5484ff6e4c0d49a30aff29f1c6cbd2cf9d3c6651ccb29c9d00f265 1767 
bsd-finger_0.17-15.2.dsc
 e95d565a90fa3ce2556242a5b8f4dd41e20dbd179b2ee155dccae8f52e850894 0 
bsd-finger_0.17-15.2.debian.tar.bz2
 79cd9c5d9979ac2e5a977f3780758893ac967aec0712de94716c68593faf8875 6824 
bsd-finger_0.17-15.2_powerpc.buildinfo
Files:
 85266c883dc5be54b5f03bb92219ba73 1767 net optional bsd-finger_0.17-15.2.dsc
 02c3cb158498087ba3b99b9f4f22fcab 0 net optional 
bsd-finger_0.17-15.2.debian.tar.bz2
 b2b44c1739c0d02835e2f42a5ffcc52d 6824 net optional 
bsd-finger_0.17-15.2_powerpc.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEWXMI+726A12MfJXdxCxY61kUkv0FAlwLvigACgkQxCxY61kU
kv0Kug//S0FJdXWmvhVlyHlS8Yy66H+V9ui/+h7CLeiEAgrngkALuJcNXFEUy9N5
tqBEJviaAi5HQ171D2c0DC6f9WcnjuYpdb5DHHGHkr/5Ytiumxld8sQ6zEmxpbAE
QAmu3Q8Gr9BQwRkTDXJ63TYHzLtOtSHC5eSQJusGF628FYGGHUgCmuRJl7IVqPGg
R5lQ+USUTeFHwTz2lUuHu7nMj+3Rao7OMuDmm0NVdLdz5l2kl8vcPlqrR6tL6HBd
k9GiicXsT1b+/JIU65bxEKtOXD3QAHcHCPOtRj0EjMfJ+FFU+RPWlAO5G7iNhVkM
BUhFOIELaFqhfCnYzOBtvchqNqKhTfs0o5rZWI7Il60KD5BjRpyLNniF+PKdNbFi
aXyKNsJbuEHT/LgRsohF2b8DlUlLE+DwOVbmfxrZgR4HswX/OnvfhFcCZYZDPcsB
UZSmBviOZJaDAoMerUx2QnZQtbKEzcA0pHWSddwWEXN8qkSmQ9JbR2pMSU1CXdHM
HZRcptfwPH5UUp95335ysrN8EQciRC6Rk72YrUT7gc3UVB4Vi5ouEADrhVEefrsM
pt3uqjIiwGcykpCNSyCxDyZyEBb5yjV5RCo2upFjIYR0u/wzspsMbjsrjgjYtvxF
4snnECToXUWux093dSc2NwltbvaSPDnk1nlM1xtHXWE45PI55x4=
=ZKnM
-END PGP SIGNATURE End Message ---

Bug#912120: marked as done (biff misses the generator for configure)

[Debian Bug Tracking System]

Your message dated Tue, 18 Dec 2018 13:49:28 +
with message-id 
and subject line Bug#912120: fixed in biff 1:0.17.pre2412-5.1
has caused the Debian Bug report #912120,
regarding biff misses the generator for configure
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.)


-- 
912120: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912120
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: netkit-ntalk
Version: 0.17-15
Severity: serious
Justification: DFSG #2
User: helm...@debian.org
Usertags: rebootstrap

The configure file in the netkit-ntalk is generated using confgen from
MCONFIG.in. However, the generator is missing. No package in unstable
contains said confgen tool. Thus configure cannot be regenerated after
fixing a bug. That's a violation of DFSG #2.

Helmut
--- End Message ---
--- Begin Message ---
Source: biff
Source-Version: 1:0.17.pre2412-5.1

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

Debian distribution maintenance software
pp.
Christoph Biedl  (supplier of updated biff 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 08 Dec 2018 10:33:07 +0100
Source: biff
Binary: biff
Architecture: source
Version: 1:0.17.pre2412-5.1
Distribution: unstable
Urgency: medium
Maintainer: Dave Holland 
Changed-By: Christoph Biedl 
Description:
 biff   - a mail notification tool
Closes: 777290 912120
Changes:
 biff (1:0.17.pre2412-5.1) unstable; urgency=medium
 .
   * Non-maintainer upload
   * Use cmake as build system, switch to debhelper.
 Closes: #777290, #912120
Checksums-Sha1:
 b4a765094c0fd3b592a81771d6c521ce9d4472e0 1712 biff_0.17.pre2412-5.1.dsc
 65d30391d289940f5f79e0ee93ad6cdae8f0c79b 4656 
biff_0.17.pre2412-5.1.debian.tar.xz
 e9e4e6c262c8660c8ff64e9f6f8c4631fa587eee 6369 
biff_0.17.pre2412-5.1_powerpc.buildinfo
Checksums-Sha256:
 ed16ce79b77fec50d1da533e81eb9ec5ed4b3bb38c4d95c5cf843954bd85b03b 1712 
biff_0.17.pre2412-5.1.dsc
 d441c1d1480b7924b1fb51cc4bcc49dc35a6121add3782031e403f2ff31324fa 4656 
biff_0.17.pre2412-5.1.debian.tar.xz
 e0436d99f92a61281493195fa78c7fd56e781d4edb408756663228e4384769d5 6369 
biff_0.17.pre2412-5.1_powerpc.buildinfo
Files:
 16330ffe283b01d05f54d72c9f266055 1712 mail extra biff_0.17.pre2412-5.1.dsc
 a0383fe284f8eb477130013a9fcbc615 4656 mail extra 
biff_0.17.pre2412-5.1.debian.tar.xz
 c98836472a47a7ccb40281033f20e015 6369 mail extra 
biff_0.17.pre2412-5.1_powerpc.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEWXMI+726A12MfJXdxCxY61kUkv0FAlwLviwACgkQxCxY61kU
kv3vtxAAo/Dn1z1IaXHxTx42SvCRqq3vJ4WE5KKun/2wUBrBq569N1i3h+5jfNoh
kak9a9bM/dQEcY8vs5D9JIBHr5IC4MTLFH4WBbV3nEVKLYZo/NDTlVqjhPEmvJ5I
/70giiP6IYXznswfXDw6wtEFd4p8DlgZxeSfxXQlXrhujD+bv454hH3gvT6znds9
GDG4mgjEgUEZNrrz357pxGuHJqVIqkkEPnWf9v8herXfhQ0zWhWVyT8lNgu7VRst
Tbji2cjmZRG1xFm4XMN4na4t3j8kYncPS5faEkY6vGeW6H8WqwYFUjdGD/ALzx+X
XBF55i7UU4ejgC2QN+HXKrcxTXeVMp3BcC2Imb3Ymk12VA0YJHIIXl8H3Oi0ElCv
HGNo5Y/hmkM6UG5oPhfCzQaIEWtD7HjM00WyQM/FN4EwHZUb69kRQ9blrALzvDtC
RkAncbLVfJB9izq9D8RKRnl22mjEi2qGFtfukmtdsttUaYRmPGKitpd8g4UuoIh3
16zFqPBL/VLFjf0gQLf95X6dM3fofojm6KlZ1y8K891nxQDXwbYEV8Z53Hxzs2OG
OpSFevmPt50htvbJSG8K1WsvBdJRai33FR4MHHd4gkeEFxDwwVoE5bNtbIMDOotI
Qs9L6LPWapsZVMUvesaGquQbdeOc/QEOWVSG4meVbKWsSlwZlPI=
=ZMtf
-END PGP SIGNATURE End Message ---

Bug#873085: marked as done (bsd-finger does not trap errors from ./configure)

[Debian Bug Tracking System]

Your message dated Tue, 18 Dec 2018 13:49:34 +
with message-id 
and subject line Bug#873085: fixed in bsd-finger 0.17-15.2
has caused the Debian Bug report #873085,
regarding bsd-finger does not trap errors from ./configure
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.)


-- 
873085: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873085
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bsd-finger
Version: 0.17-15.1
Severity: serious
Justification: policy 4.6
User: helm...@debian.org
Usertags: rebootstrap

The debian policy section 4.6 requires that when build commands fail,
the build should abort. In case bsd-finger's ./configure aborts, the
error is ignored and the build attempts to continue potentially
resulting in a broken package. Adding "set -e; " (as suggested by the
policy) before the conditional fixes this issue.

Helmut
--- End Message ---
--- Begin Message ---
Source: bsd-finger
Source-Version: 0.17-15.2

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

Debian distribution maintenance software
pp.
Christoph Biedl  (supplier of updated 
bsd-finger package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 08 Dec 2018 10:36:30 +0100
Source: bsd-finger
Binary: finger fingerd
Architecture: source
Version: 0.17-15.2
Distribution: unstable
Urgency: medium
Maintainer: Anibal Monsalve Salazar 
Changed-By: Christoph Biedl 
Description:
 finger - user information lookup program
 fingerd- remote user information server
Closes: 873085 912121
Changes:
 bsd-finger (0.17-15.2) unstable; urgency=medium
 .
   * Non-maintainer upload
   * Use cmake as build system. Closes: #873085, #912121
Checksums-Sha1:
 6b3d3062af7e3eed62f462dd55a0c8d5441c4a63 1767 bsd-finger_0.17-15.2.dsc
 417e00a4b004d4a14fc65d78bda642f1cbb8effc 0 
bsd-finger_0.17-15.2.debian.tar.bz2
 d6a82691d91c763045e594fd945bfa99caa1b150 6824 
bsd-finger_0.17-15.2_powerpc.buildinfo
Checksums-Sha256:
 5b2d894d8e5484ff6e4c0d49a30aff29f1c6cbd2cf9d3c6651ccb29c9d00f265 1767 
bsd-finger_0.17-15.2.dsc
 e95d565a90fa3ce2556242a5b8f4dd41e20dbd179b2ee155dccae8f52e850894 0 
bsd-finger_0.17-15.2.debian.tar.bz2
 79cd9c5d9979ac2e5a977f3780758893ac967aec0712de94716c68593faf8875 6824 
bsd-finger_0.17-15.2_powerpc.buildinfo
Files:
 85266c883dc5be54b5f03bb92219ba73 1767 net optional bsd-finger_0.17-15.2.dsc
 02c3cb158498087ba3b99b9f4f22fcab 0 net optional 
bsd-finger_0.17-15.2.debian.tar.bz2
 b2b44c1739c0d02835e2f42a5ffcc52d 6824 net optional 
bsd-finger_0.17-15.2_powerpc.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEWXMI+726A12MfJXdxCxY61kUkv0FAlwLvigACgkQxCxY61kU
kv0Kug//S0FJdXWmvhVlyHlS8Yy66H+V9ui/+h7CLeiEAgrngkALuJcNXFEUy9N5
tqBEJviaAi5HQ171D2c0DC6f9WcnjuYpdb5DHHGHkr/5Ytiumxld8sQ6zEmxpbAE
QAmu3Q8Gr9BQwRkTDXJ63TYHzLtOtSHC5eSQJusGF628FYGGHUgCmuRJl7IVqPGg
R5lQ+USUTeFHwTz2lUuHu7nMj+3Rao7OMuDmm0NVdLdz5l2kl8vcPlqrR6tL6HBd
k9GiicXsT1b+/JIU65bxEKtOXD3QAHcHCPOtRj0EjMfJ+FFU+RPWlAO5G7iNhVkM
BUhFOIELaFqhfCnYzOBtvchqNqKhTfs0o5rZWI7Il60KD5BjRpyLNniF+PKdNbFi
aXyKNsJbuEHT/LgRsohF2b8DlUlLE+DwOVbmfxrZgR4HswX/OnvfhFcCZYZDPcsB
UZSmBviOZJaDAoMerUx2QnZQtbKEzcA0pHWSddwWEXN8qkSmQ9JbR2pMSU1CXdHM
HZRcptfwPH5UUp95335ysrN8EQciRC6Rk72YrUT7gc3UVB4Vi5ouEADrhVEefrsM
pt3uqjIiwGcykpCNSyCxDyZyEBb5yjV5RCo2upFjIYR0u/wzspsMbjsrjgjYtvxF
4snnECToXUWux093dSc2NwltbvaSPDnk1nlM1xtHXWE45PI55x4=
=ZKnM
-END PGP SIGNATURE End Message ---

Bug#916777: activemq: broken symlinks: /usr/share/activemq/lib/{geronimo-jacc_1.1_spec,optional/{commons-httpclient,stax-api}}.jar

[Andreas Beckmann]

Package: activemq
Version: 5.15.8-1
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...):

0m53.7s ERROR: FAIL: Broken symlinks:
  /usr/share/activemq/lib/geronimo-jacc_1.1_spec.jar -> 
../../java/geronimo-jacc_1.1_spec.jar (activemq)
  /usr/share/activemq/lib/optional/stax-api.jar -> ../../../java/stax-api.jar 
(activemq)
  /usr/share/activemq/lib/optional/commons-httpclient.jar -> 
../../../java/commons-httpclient.jar (activemq)

Given that one .jar file is not marked as optional, I set the severity
to serious, since there seems to be a dependency missing.

Should activemq Recommends/Suggests the packages providing the optional
.jar files?


cheers,

Andreas


activemq_5.15.8-1.log.gz
Description: application/gzip

Bug#916774: linux-perf metapackage fails to upgrade due to file conflict between linux-perf-4.18 & linux-perf-4.19

[Paul Wise]

Package: linux-perf-4.19
Version: 4.19.9-1
Severity: serious

I had the linux-perf metapackage fail to upgrade due to a file conflict
between linux-perf-4.18 & linux-perf-4.19:

$ sudo apt install -t unstable linux-perf
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following package was automatically installed and is no longer required:
  linux-perf-4.18
Use 'sudo apt autoremove' to remove it.
The following additional packages will be installed:
  linux-perf-4.19
Suggested packages:
  linux-doc-4.19
The following NEW packages will be installed:
  linux-perf-4.19
The following packages will be upgraded:
  linux-perf
1 upgraded, 1 newly installed, 0 to remove and 338 not upgraded.
Need to get 0 B/1,491 kB of archives.
After this operation, 6,614 kB of additional disk space will be used.
Do you want to continue? [Y/n] 
Reading changelogs... Done
Selecting previously unselected package linux-perf-4.19.
(Reading database ... 456870 files and directories currently installed.)
Preparing to unpack .../linux-perf-4.19_4.19.9-1_amd64.deb ...
Unpacking linux-perf-4.19 (4.19.9-1) ...
dpkg: error processing archive 
/var/cache/apt/archives/linux-perf-4.19_4.19.9-1_amd64.deb (--unpack):
 trying to overwrite '/usr/lib/perf/examples/bpf/5sec.c', which is also in 
package linux-perf-4.18 4.18.20-2
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Preparing to unpack .../linux-perf_4.19+101_all.deb ...
Unpacking linux-perf (4.19+101) over (4.18+100) ...
Errors were encountered while processing:
 /var/cache/apt/archives/linux-perf-4.19_4.19.9-1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

$ echo $?
100

$ sudo dpkg --force-all --purge linux-perf-4.18
(Reading database ... 456869 files and directories currently installed.)
Removing linux-perf-4.18 (4.18.20-2) ...
Processing triggers for man-db (2.8.4-3) ...

$ sudo apt --fix-broken install -t unstable 
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Correcting dependencies... Done
The following additional packages will be installed:
  linux-perf-4.19
Suggested packages:
  linux-doc-4.19
The following NEW packages will be installed:
  linux-perf-4.19
0 upgraded, 1 newly installed, 0 to remove and 338 not upgraded.
1 not fully installed or removed.
Need to get 0 B/1,484 kB of archives.
After this operation, 6,614 kB of additional disk space will be used.
Do you want to continue? [Y/n] 
Selecting previously unselected package linux-perf-4.19.
(Reading database ... 45 files and directories currently installed.)
Preparing to unpack .../linux-perf-4.19_4.19.9-1_amd64.deb ...
Unpacking linux-perf-4.19 (4.19.9-1) ...
Setting up linux-perf-4.19 (4.19.9-1) ...
Processing triggers for man-db (2.8.4-3) ...
Setting up linux-perf (4.19+101) ...

-- System Information:
Debian Release: buster/sid
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 
'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 
'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.18.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8), 
LANGUAGE=en_AU.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages linux-perf-4.19 depends on:
ii  libbabeltrace1  1.5.6-2
ii  libc6   2.28-2
ii  libdw1  0.175-1
ii  libelf1 0.175-1
ii  liblzma55.2.2-1.3
ii  libnuma12.0.12-1
ii  libperl5.28 5.28.1-3
ii  libpython3.73.7.2~rc1-1
ii  libslang2   2.3.2-1+b1
ii  libunwind8  1.2.1-8
ii  perl5.28.1-3
ii  python3 3.6.7-1
ii  zlib1g  1:1.2.11.dfsg-1

Versions of packages linux-perf-4.19 recommends:
ii  linux-base  4.5

Versions of packages linux-perf-4.19 suggests:
pn  linux-doc-4.19  

-- no debconf information

-- 
bye,
pabs

https://wiki.debian.org/PaulWise



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

Bug#915335: marked as done (checkstyle FTBFS: head() in com.puppycrawl.tools.checkstyle.xpath.AbstractNode cannot implement head() in net.sf.saxon.om.Item)

[Debian Bug Tracking System]

Your message dated Tue, 18 Dec 2018 13:04:21 +
with message-id 
and subject line Bug#915335: fixed in checkstyle 8.15-1
has caused the Debian Bug report #915335,
regarding checkstyle FTBFS: head() in 
com.puppycrawl.tools.checkstyle.xpath.AbstractNode cannot implement head() in 
net.sf.saxon.om.Item
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.)


-- 
915335: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915335
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: checkstyle
Version: 8.14-1
Severity: serious
Tags: ftbfs

Some recent change in unstable makes checkstyle FTBFS:

https://tests.reproducible-builds.org/debian/history/checkstyle.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/checkstyle.html

...
[INFO] -
[ERROR] COMPILATION ERROR : 
[INFO] -
[ERROR] 
/build/1st/checkstyle-8.14/src/main/java/com/puppycrawl/tools/checkstyle/xpath/AbstractNode.java:[279,23]
 head() in com.puppycrawl.tools.checkstyle.xpath.AbstractNode cannot implement 
head() in net.sf.saxon.om.Item
  return type net.sf.saxon.om.Item is not compatible with 
net.sf.saxon.om.NodeInfo
[ERROR] 
/build/1st/checkstyle-8.14/src/main/java/com/puppycrawl/tools/checkstyle/xpath/AbstractNode.java:[278,5]
 method does not override or implement a method from a supertype
[ERROR] 
/build/1st/checkstyle-8.14/src/main/java/com/puppycrawl/tools/checkstyle/filters/XpathFilter.java:[190,45]
 incompatible types: java.util.List> cannot be 
converted to java.util.List
[ERROR] 
/build/1st/checkstyle-8.14/src/main/java/com/puppycrawl/tools/checkstyle/xpath/ElementNode.java:[38,8]
 com.puppycrawl.tools.checkstyle.xpath.ElementNode is not abstract and does not 
override abstract method head() in net.sf.saxon.om.GroundedValue
[ERROR] 
/build/1st/checkstyle-8.14/src/main/java/com/puppycrawl/tools/checkstyle/xpath/RootNode.java:[39,8]
 com.puppycrawl.tools.checkstyle.xpath.RootNode is not abstract and does not 
override abstract method head() in net.sf.saxon.om.GroundedValue
[ERROR] 
/build/1st/checkstyle-8.14/src/main/java/com/puppycrawl/tools/checkstyle/xpath/AttributeNode.java:[31,8]
 com.puppycrawl.tools.checkstyle.xpath.AttributeNode is not abstract and does 
not override abstract method head() in net.sf.saxon.om.GroundedValue
[INFO] 6 errors 
--- End Message ---
--- Begin Message ---
Source: checkstyle
Source-Version: 8.15-1

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

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated checkstyle 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: Tue, 18 Dec 2018 13:50:05 +0100
Source: checkstyle
Binary: checkstyle checkstyle-doc
Architecture: source
Version: 8.15-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Description:
 checkstyle - checks Java source against a coding standard
 checkstyle-doc - Documentation for Checkstyle
Closes: 915335
Changes:
 checkstyle (8.15-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream release
 - Refreshed the patches
 - Depend on libpicocli-java instead of libcommons-cli-java
 - Fixes the compatibility with saxonhe 9.9.0.2 (Closes: #915335)
Checksums-Sha1:
 e5932aabb4c235c33594dd53c47923fcde3aa246 2488 checkstyle_8.15-1.dsc
 a94f903c6f6bca5199f8d7d3bbf90478a682fceb 3661344 checkstyle_8.15.orig.tar.xz
 07f499dbc4c054a9472069b2de077f1160745a4d 7912 checkstyle_8.15-1.debian.tar.xz
 fdc7778c72f7b039c803a3e36431ff7a769cedaf 17992 
checkstyle_8.15-1_source.buildinfo
Checksums-Sha256:
 91fece6c94f66c99e773a254ca67ad0df3fb2823542052344495e31c09aaef7f 2488 
checkstyle_8.15-1.dsc
 cefa1a1d1bf27ec5144035bb1018af2d21d7ccc2aa4fa9ac68680a0c6259930a 3661344 
checkstyle_8.15.orig.tar.xz
 6c738a1f886f6741da212dc1d05f56444620fdfe7e49004f418b7175c2133012 7912 
checkstyle_8.15-1.debian.tar.xz
 

Processed: Re: Bug#916699: Run minissdpd debconf question insufficiently detailed for an advanced user to answer it

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #916699 [minissdpd] Run minissdpd debconf question insufficiently detailed 
for an advanced user to answer it
Severity set to 'serious' from 'normal'

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

Bug#916772: pkg-config: missing Depends: dpkg-dev

[Helmut Grohne]

Package: pkg-config
Version: 0.29-4+b1
Severity: serious
Justification: missing dependency

# i686-linux-gnu-pkg-config --libs libssl
Package libssl was not found in the pkg-config search path.
Perhaps you should add the directory containing `libssl.pc'
to the PKG_CONFIG_PATH environment variable
No package 'libssl' found
# ls /usr/lib/i386-linux-gnu/pkgconfig/libssl.pc 
/usr/lib/i386-linux-gnu/pkgconfig/libssl.pc
# apt -y install dpkg-dev
...
# i686-linux-gnu-pkg-config --libs libssl
-lssl
#

In this case, i686-linux-gnu-pkg-config is a symlink to
/usr/share/pkg-config-crosswrapper and that script has the following
line:

  multiarch="`dpkg-architecture -t"${triplet}" -qDEB_HOST_MULTIARCH 
2>/dev/null`"

It calls dpkg-architecture (which is in dpkg-dev) and igores all errors.
In the absence of dpkg-architecture, the result will be empty and
pkg-config doesn't work.

If adding dpkg-dev to Depends is not desired, the cross-wrapper could be
extended to give a useful error message in case $multiarch is empty:

--- /usr/share/pkg-config-crosswrapper
+++ /usr/share/pkg-config-crosswrapper
@@ -11,6 +11,10 @@
   triplet="${basename%-pkg-config}"
   # Normalized multiarch path if any, e.g. i386-linux-gnu for i386
   multiarch="`dpkg-architecture -t"${triplet}" -qDEB_HOST_MULTIARCH 
2>/dev/null`"
+  if test "$?" != 0; then
+echo "Please apt install dpkg-dev to use this program." 1>&2
+exit 1
+  fi
   # Native multiarch path
   native_multiarch="$(cat /usr/lib/pkg-config.multiarch)"
 

dpkg-dev should be added to Recommends in that case.

Helmut

Bug#916768: libelogind-dev-doc: missing Breaks+Replaces: libelogind-dev (<< 239.1+20181115-1)

[Andreas Beckmann]

Package: libelogind-dev-doc
Version: 239.3-3+debian1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Preparing to unpack .../libelogind-dev-doc_239.3-3+debian1_all.deb ...
  Unpacking libelogind-dev-doc (239.3-3+debian1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libelogind-dev-doc_239.3-3+debian1_all.deb (--unpack):
   trying to overwrite '/usr/share/man/man3/sd-bus.3.gz', which is also in 
package libelogind-dev:amd64 239.1+20181112+gd4a3f291e395+nosubmodule-1+debian1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/libelogind-dev-doc_239.3-3+debian1_all.deb


cheers,

Andreas

PS: please use a normal debian revision in the version, i.e. only number


libelogind-dev=239.1+20181112+gd4a3f291e395+nosubmodule-1+debian1_libelogind-dev-doc=239.3-3+debian1.log.gz
Description: application/gzip

Processed: user debian...@lists.debian.org, usertagging 916673, found 891612 in 6.5.1-3 ...

[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 916673 piuparts
There were no usertags set.
Usertags are now: piuparts.
> found 891612 6.5.1-3
Bug #891612 [thumbor] thumbor: uninstallable after python-imaging removal
Marked as found in versions thumbor/6.5.1-3.
> found 914966 4.19.9-1
Bug #914966 [linux-perf-4.19] linux-perf-4.19: missing Breaks+Replaces: 
linux-perf-4.18
Marked as found in versions linux/4.19.9-1.
> thanks
Stopping processing here.

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

Bug#916767: python-dmidecode-data: missing Breaks+Replaces: python-dmidecode (<< 3.12.2-5)

[Andreas Beckmann]

Package: python-dmidecode-data
Version: 3.12.2-5
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Preparing to unpack .../python-dmidecode-data_3.12.2-5_all.deb ...
  Unpacking python-dmidecode-data (3.12.2-5) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python-dmidecode-data_3.12.2-5_all.deb (--unpack):
   trying to overwrite '/usr/share/python-dmidecode/pymap.xml', which is also 
in package python-dmidecode 3.12.2-4
  Errors were encountered while processing:
   /var/cache/apt/archives/python-dmidecode-data_3.12.2-5_all.deb


cheers,

Andreas


python-dmidecode=3.12.2-4_python-dmidecode-data=3.12.2-5.log.gz
Description: application/gzip

Bug#916766: libucto3: missing Breaks+Replaces: libucto2

[Andreas Beckmann]

Package: libucto3
Version: 0.14-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
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...):

  Selecting previously unselected package libucto3:amd64.
  Preparing to unpack .../libucto3_0.14-1_amd64.deb ...
  Unpacking libucto3:amd64 (0.14-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libucto3_0.14-1_amd64.deb (--unpack):
   trying to overwrite '/usr/share/ucto/textcat.cfg', which is also in package 
libucto2:amd64 0.9.6-1+b1
  Errors were encountered while processing:
   /var/cache/apt/archives/libucto3_0.14-1_amd64.deb


cheers,

Andreas


libucto2=0.9.6-1+b1_libucto3=0.14-1.log.gz
Description: application/gzip

Bug#916764: znc-backlog: overly strict dependency on znc?

[Andreas Beckmann]

Package: znc-backlog
Version: 0.20170713-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

do you really need a dependency on the exact binary version of znc
available at the build time of znc-backlog? I.e., every time znc
gets uploaded *or binNMUed*, a binNMU of znc-backlog is needed, too.
Wouldn't a dependency computed from the upstream version be sufficient?
E.g. znc (>= ${znc:upstreamversion}), znc (<< ${znc:upstreamversion}+)


Andreas

Bug#911610: eldav: files missing after upgrade from stretch: /usr/share/emacs/site-lisp/eldav/{,vc-}eldav.el

[Andreas Beckmann]

On 2018-12-18 10:57, Tatsuya Kinoshita wrote:
>> I've also observed this behavior (i.e. lost files in some package, e.g.
>> eldav) in stretch, so it's probably apel there, too.
> 
> I think apel 10.8+0.20120427-16 in stretch is fine, because the
> `emacs` flavor is skipped in the emacsen-install script.
> 
> The problem is caused when unversioned emacs flavor (emacs >=
> 1:25.2+1-7) and apel 10.8+0.20120427-17 or -18 are installed.
> 
> Please tell me the details if you really think apel
> 10.8+0.20120427-16 is problematic.
OK, I'll rerun some tests and check again. Maybe repeat this after apel
migrated to testing.


Andreas

Processed: user debian...@lists.debian.org, usertagging 914733, found 914733 in 5.8.0+dfsg-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 914733 piuparts
There were no usertags set.
Usertags are now: piuparts.
> found 914733 5.8.0+dfsg-1
Bug #914733 {Done: Dmitry Smirnov } [civicrm-common] 
civicrm-common: Depends: php-psr-log (< 1.1~~) but 1.1.0-1 is to be installed
Marked as found in versions civicrm/5.8.0+dfsg-1; no longer marked as fixed in 
versions civicrm/5.8.0+dfsg-1 and reopened.
> thanks
Stopping processing here.

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

Processed: tagging 916576, found 857954 in 2:1.02.153-1, affects 911861, user debian...@lists.debian.org ...

[Debian Bug Tracking System]

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

> tags 916576 + sid buster
Bug #916576 [src:pbdagcon] pbdagcon: FTBFS pbdata/Types.h: No such file or 
directory
Added tag(s) sid and buster.
> found 857954 2:1.02.153-1
Bug #857954 [libdevmapper-dev] libdevmapper-dev: broken symlink: 
/usr/lib//libdevmapper-event-lvm2.so -> 
/lib//libdevmapper-event-lvm2.so.2.02
Ignoring request to alter found versions of bug #857954 to the same values 
previously set
> affects 911861 + python3-hbmqtt
Bug #911861 [src:python-hbmqtt] python-hbmqtt FTBFS with Python 3.7
Added indication that 911861 affects python3-hbmqtt
> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
> usertags 911861 piuparts
There were no usertags set.
Usertags are now: piuparts.
> found 915023 0.9.0-2
Bug #915023 [python3-senlin-dashboard] openstack-dashboard: fails to install in 
buster along python3-senlin-dashboard
Marked as found in versions senlin-dashboard/0.9.0-2.
> thanks
Stopping processing here.

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

Bug#915509: scala ftbfs: The repository system could not be initialized

[Emmanuel Bourg]

Control: reassign -1 libaether-ant-tasks-java
Control: affects -1 src:scala
Control: severity -1 important

This is actually an issue with libaether-ant-tasks-java, the classpath
of aether-ant-tasks.jar is missing slf4j-api.jar. This issue was
probably triggered by the update of Maven to the version 3.6.

Emmanuel Bourg

Bug#916761: deepin-icon-theme: fails to install: update-alternatives: error: alternative path /usr/share/icons/deepin/cursor.theme doesn't exist

[Andreas Beckmann]

Package: deepin-icon-theme
Version: 15.12.67-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

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

  Setting up deepin-icon-theme (15.12.67-1) ...
  update-alternatives: error: alternative path 
/usr/share/icons/deepin/cursor.theme doesn't exist
  dpkg: error processing package deepin-icon-theme (--configure):
   installed deepin-icon-theme package post-installation script subprocess 
returned error exit status 2
  Errors were encountered while processing:
   deepin-icon-theme


cheers,

Andreas


deepin-icon-theme_15.12.67-1.log.gz
Description: application/gzip

Processed: Re: Bug#915509: scala ftbfs: The repository system could not be initialized

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 libaether-ant-tasks-java
Bug #915509 [src:scala] scala ftbfs: The repository system could not be 
initialized
Bug reassigned from package 'src:scala' to 'libaether-ant-tasks-java'.
No longer marked as found in versions scala/2.11.12-4.
Ignoring request to alter fixed versions of bug #915509 to the same values 
previously set
> affects -1 src:scala
Bug #915509 [libaether-ant-tasks-java] scala ftbfs: The repository system could 
not be initialized
Added indication that 915509 affects src:scala
> severity -1 important
Bug #915509 [libaether-ant-tasks-java] scala ftbfs: The repository system could 
not be initialized
Severity set to 'important' from 'serious'

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

Bug#911610: eldav: files missing after upgrade from stretch: /usr/share/emacs/site-lisp/eldav/{,vc-}eldav.el

[Tatsuya Kinoshita]

Control: notfound -1 10.8+0.20120427-16
Control: found -1 10.8+0.20120427-17

On December 17, 2018 at 11:22PM +0100, anbe (at debian.org) wrote:
> Followup-For: Bug #911610
> Control: found -1 10.8+0.20120427-16
>
> I've also observed this behavior (i.e. lost files in some package, e.g.
> eldav) in stretch, so it's probably apel there, too.

I think apel 10.8+0.20120427-16 in stretch is fine, because the
`emacs` flavor is skipped in the emacsen-install script.

The problem is caused when unversioned emacs flavor (emacs >=
1:25.2+1-7) and apel 10.8+0.20120427-17 or -18 are installed.

Please tell me the details if you really think apel
10.8+0.20120427-16 is problematic.

Thanks,
--
Tatsuya Kinoshita


pgp4QCq_HAr20.pgp
Description: PGP signature

Processed: Re: Bug#911610: eldav: files missing after upgrade from stretch: /usr/share/emacs/site-lisp/eldav/{,vc-}eldav.el

[Debian Bug Tracking System]

Processing control commands:

> notfound -1 10.8+0.20120427-16
Bug #911610 {Done: Tatsuya Kinoshita } [apel] eldav: files 
missing after upgrade from stretch: 
/usr/share/emacs/site-lisp/eldav/{,vc-}eldav.el
Bug #911612 {Done: Tatsuya Kinoshita } [apel] tdiary-mode: 
files missing after upgrade from stretch: 
/usr/share/emacs/site-lisp/tdiary-mode/{http,tdiary-mode}.el
No longer marked as found in versions apel/10.8+0.20120427-16.
No longer marked as found in versions apel/10.8+0.20120427-16.
> found -1 10.8+0.20120427-17
Bug #911610 {Done: Tatsuya Kinoshita } [apel] eldav: files 
missing after upgrade from stretch: 
/usr/share/emacs/site-lisp/eldav/{,vc-}eldav.el
Bug #911612 {Done: Tatsuya Kinoshita } [apel] tdiary-mode: 
files missing after upgrade from stretch: 
/usr/share/emacs/site-lisp/tdiary-mode/{http,tdiary-mode}.el
Marked as found in versions apel/10.8+0.20120427-17.
Marked as found in versions apel/10.8+0.20120427-17.

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

Processed: bug 914524 is forwarded to https://sogo.nu/bugs/view.php?id=4625

[Debian Bug Tracking System]

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

> forwarded 914524 https://sogo.nu/bugs/view.php?id=4625
Bug #914524 [sogo] sogo: SSL problem(?) causes 'An error occurred during object 
publishing' in webmail
Set Bug forwarded-to-address to 'https://sogo.nu/bugs/view.php?id=4625'.
> thanks
Stopping processing here.

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

Bug#914524: Forwarded upstream

[Jordi Mallach]

I have forwarded this upstream, here:

https://sogo.nu/bugs/view.php?id=4625

-- 
Jordi Mallach Pérez  --  Debian developer http://www.debian.org/
jo...@sindominio.net jo...@debian.org http://www.sindominio.net/
GnuPG public key information available at http://oskuro.net/


signature.asc
Description: PGP signature

Bug#916468: Conflict over /usr/bin/dune

[Stéphane Glondu]

Hi,

It has been brought to my attention that both packages "whitedune" and
"dune" provide the binary "/usr/bin/dune" (#916468).

The situation falls directly under section 10.1 of the Policy:

https://www.debian.org/doc/debian-policy/ch-files.html#s-binaries

> Two different packages must not install programs with different
> functionality but with the same filenames.

The solution proposed by the policy is to rename one or both of the
packages, after a discussion here:

> [...] try to find a consensus about which program will have to be
> renamed. If a consensus cannot be reached, both programs must be
> renamed.

The "dune" package (of which I am the maintainer) is a popular build
system for OCaml projects. It is pretty recent, has strong upstream
support, and more and more projects are switching to it, which is a
reason to have it in Debian.

It was previously named jbuilder, but has been renamed due to a conflict
with another software. Upstream is reluctant to rename it again.

The "whitedune" package is a graphical VRML97/X3D viewer, editor, 3D
modeller and animation tool. It has existed in Debian since 2007 and its
last upload to Debian (an NMU) dates back to March 2016. The version in
Debian is 0.30.10 while the last upstream version [1] seems to be
0.99pl1234. The source tarball seems to date back to December 2018, so
the upstream project seems well alive. In the "whitedune" package,
"/usr/bin/dune" is a symbolic link to "whitedune".

[1] http://wdune.ourproject.org/

Due to its nature, the build system (a command line tool) is more likely
(IMHO) to be invoked as "dune" by third-parties than the desktop
application. Moreover, the existence of the symlink suggests that the
preferred way to call the application is through "whitedune" (and a menu
entry exists). Therefore, I propose that the "whitedune" package drops
the "/usr/bin/dune" symlink altogether.


Cheers,

-- 
Stéphane

Bug#916706: marked as done (python-cobra FTBFS with python-pip 18.1)

[Debian Bug Tracking System]

Your message dated Tue, 18 Dec 2018 09:04:53 +
with message-id 
and subject line Bug#916706: fixed in python-cobra 0.14.1-1
has caused the Debian Bug report #916706,
regarding python-cobra FTBFS with python-pip 18.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.)


-- 
916706: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916706
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-cobra
Version: 0.13.4-2
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-cobra.html

...
= test session starts ==
platform linux -- Python 3.6.8rc1, pytest-3.10.1, py-1.7.0, pluggy-0.8.0
benchmark: 3.1.1 (defaults: timer=time.perf_counter disable_gc=False 
min_rounds=5 min_time=0.05 max_time=1.0 calibration_precision=10 
warmup=False warmup_iterations=10)
rootdir: /build/1st/python-cobra-0.13.4, inifile: setup.cfg
plugins: benchmark-3.1.1
collected 0 items / 1 errors

 ERRORS 
__ ERROR collecting  ___
/usr/lib/python3/dist-packages/_pytest/config/__init__.py:430: in 
_importconftest
return self._conftestpath2mod[conftestpath]
E   KeyError: 
local('/build/1st/python-cobra-0.13.4/.pybuild/cpython3_3.6_cobra/build/cobra/test/conftest.py')

During handling of the above exception, another exception occurred:
/usr/lib/python3/dist-packages/pipdeptree.py:17: in 
from pip._internal import get_installed_distributions
E   ImportError: cannot import name 'get_installed_distributions'

During handling of the above exception, another exception occurred:
/usr/lib/python3/dist-packages/_pytest/config/__init__.py:436: in 
_importconftest
mod = conftestpath.pyimport()
/usr/lib/python3/dist-packages/py/_path/local.py:668: in pyimport
__import__(modname)
cobra/__init__.py:11: in 
from cobra import flux_analysis, io
cobra/flux_analysis/__init__.py:3: in 
from cobra.flux_analysis.gapfilling import gapfill
cobra/flux_analysis/gapfilling.py:8: in 
from cobra.core import Model
cobra/core/__init__.py:6: in 
from cobra.core.gene import Gene
cobra/core/gene.py:13: in 
from cobra.util import resettable
cobra/util/__init__.py:7: in 
from cobra.util.util import *
cobra/util/util.py:5: in 
from depinfo import print_dependencies
/usr/lib/python3/dist-packages/depinfo/__init__.py:27: in 
from depinfo.info import *
/usr/lib/python3/dist-packages/depinfo/info.py:24: in 
from pipdeptree import build_dist_index, construct_tree
/usr/lib/python3/dist-packages/pipdeptree.py:20: in 
from pip import get_installed_distributions, FrozenRequirement
E   ImportError: cannot import name 'get_installed_distributions'

During handling of the above exception, another exception occurred:
/usr/lib/python3/dist-packages/py/_path/common.py:377: in visit
for x in Visitor(fil, rec, ignore, bf, sort).gen(self):
/usr/lib/python3/dist-packages/py/_path/common.py:429: in gen
for p in self.gen(subdir):
/usr/lib/python3/dist-packages/py/_path/common.py:418: in gen
dirs = self.optsort([p for p in entries
/usr/lib/python3/dist-packages/py/_path/common.py:419: in 
if p.check(dir=1) and (rec is None or rec(p))])
/usr/lib/python3/dist-packages/_pytest/main.py:601: in _recurse
ihook = self.gethookproxy(dirpath)
/usr/lib/python3/dist-packages/_pytest/main.py:418: in gethookproxy
my_conftestmodules = pm._getconftestmodules(fspath)
/usr/lib/python3/dist-packages/_pytest/config/__init__.py:414: in 
_getconftestmodules
mod = self._importconftest(conftestpath)
/usr/lib/python3/dist-packages/_pytest/config/__init__.py:453: in 
_importconftest
raise ConftestImportFailure(conftestpath, sys.exc_info())
E   _pytest.config.ConftestImportFailure: 
(local('/build/1st/python-cobra-0.13.4/.pybuild/cpython3_3.6_cobra/build/cobra/test/conftest.py'),
 (, ImportError("cannot import name 
'get_installed_distributions'",), ))
=== warnings summary ===
cobra/flux_analysis/gapfilling.py:83
  
/build/1st/python-cobra-0.13.4/.pybuild/cpython3_3.6_cobra/build/cobra/flux_analysis/gapfilling.py:83:
 DeprecationWarning: invalid escape sequence \s
"""

cobra/core/gene.py:248
  
/build/1st/python-cobra-0.13.4/.pybuild/cpython3_3.6_cobra/build/cobra/core/gene.py:248:
 DeprecationWarning: invalid escape sequence \(
the_gene_re = re.compile('(^|(?<=( |\()))%s(?=( |\)|$))' %

cobra/core/gene.py:262
  

Bug#905254: Status of libphp-phpmailer

[Xavier]

Le 14/12/2018 à 09:17, Chris Lamb a écrit :
> Chris Lamb wrote:
> 
>> Vincent Danjean wrote:
>>
>>>   However, the git does not seem to have been moved to salsa.
>>
>> I fixed a number of CVEs recently and I would love to push my changes
>> to suitable branches. Can the PEAR maintainers please migrate this
>> repo ASAP?
> 
> Any update on getting this into Git...?
> 
> Regards,

Hi all,

it seems difficult to migrate libphp-phpmailer to version 6.x before
buster freeze. However, ocsinventory-server is affected by some CVEs [1]
which are fixed on version 2.5 which embeds PHPMailer 6.x.

So my question is could I embed PHPMailer-6 in ocsinventory-server ?

Cheers,
Xavier

[1] https://bugs.debian.org/905396

Bug#915050: (gitlab) Re: Bug#915050: Keep out of testing

[Alexander Wirt]

On Tue, 18 Dec 2018, Pirate Praveen wrote:

> [adding -devel to cc]
> 
> On 12/3/18 8:11 PM, Dominik George wrote:
> >> well, Debian is using gitlab!!! so this sentence has no sense. The
> >> problem here
> >> is that is a complex software that depends of a lot of pieces and it's
> >> not
> >> easy/possible to fit the definition. So, maybe we should create another
> >> category
> >> of software.
> > 
> > Yes, and that Debian officially uses GitLab, from a foreign source, without 
> > being able to support it in Debian, does make me feel ashamed for the 
> > project.
> > 
> >> maybe creating another kind of repo. debian-contributuions
> >> debian-blabla, whatever.
> >>
> > 
> > We had volatile, which, redefined properly, could help. I am trying to 
> > draft such a definition.
> 
> Did you get a chance to work on it?
> 
> I think it has to be an extension of backports with dependencies that
> fall within the backports criteria being maintained in backports and
> only packages that cannot be in backports maintained in volatile.
> 
> Original definition of volatile from https://www.debian.org/volatile/:
> "Some packages aim at fast moving targets, such as spam filtering and
> virus scanning, and even when using updated data patterns, they do not
> really work for the full time of a stable release. The main goal of
> volatile is allowing system administrators to update their systems in a
> nice, consistent way, without getting the drawbacks of using unstable,
> even without getting the drawbacks for the selected packages. So
> debian-volatile will only contain changes to stable programs that are
> necessary to keep them functional."
> 
> Proposed definition:
> "Some packages aim at fast moving targets, such as complex web based
> software with very small release cycles and new dependencies, they do
> not receive security support or bug fixes for the full time of a stable
> release. This means backporting targeted fixes are impossible.  The main
> goal of volatile is allowing system administrators to update their
> systems in a nice, consistent way, without getting the drawbacks of
> using unstable, even without getting the drawbacks for the selected
> packages. New dependencies introduced can be maintained in backports
> repository. So debian-volatile will be an extension of debian-backports,
> with dependencies that fall within the criteria maintained in
> debian-backports."
I don't think that -backports is the right suite. It should be something new,
with a new team.

Alex



signature.asc
Description: PGP signature

Bug#906371: marked as done (jmodeltest: FTBFS in buster/sid)

[Debian Bug Tracking System]

Your message dated Tue, 18 Dec 2018 08:41:54 +
with message-id 
and subject line Bug#906371: fixed in jmodeltest 2.1.10+dfsg-7
has caused the Debian Bug report #906371,
regarding jmodeltest: FTBFS in buster/sid
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.)


-- 
906371: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906371
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:jmodeltest
Version: 2.1.10+dfsg-6
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep --with javahelper
   dh_update_autotools_config -i
   dh_autoreconf -i
   dh_auto_configure -i
   jh_linkjars -i
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>/jmodeltest-2.1.10+dfsg'
dh_auto_build
ant -Duser.name debian
Buildfile: /<>/jmodeltest-2.1.10+dfsg/build.xml

compile:
[mkdir] Created dir: /<>/jmodeltest-2.1.10+dfsg/build/classes

[... snipped ...]

[javac]  ^
[javac] 
/<>/jmodeltest-2.1.10+dfsg/src/main/java/es/uvigo/darwin/jmodeltest/utilities/MyTableModel.java:284:
 warning: [deprecation] Double(double) in Double has been deprecated
[javac] data[i][8] = new Double(Round(
[javac]  ^
[javac] 
/<>/jmodeltest-2.1.10+dfsg/src/main/java/es/uvigo/darwin/jmodeltest/utilities/TableSorter.java:317:
 warning: [deprecation] getModifiers() in InputEvent has been deprecated
[javac] int shiftPressed = 
e.getModifiers()_MASK; 
[javac] ^
[javac] 
/<>/jmodeltest-2.1.10+dfsg/src/main/java/es/uvigo/darwin/jmodeltest/utilities/TableSorter.java:317:
 warning: [deprecation] SHIFT_MASK in InputEvent has been deprecated
[javac] int shiftPressed = 
e.getModifiers()_MASK; 
[javac]   ^
[javac] 
/<>/jmodeltest-2.1.10+dfsg/src/main/java/es/uvigo/darwin/jmodeltest/utilities/MyTableCellRenderer.java:55:
 warning: [deprecation] Integer(int) in Integer has been deprecated
[javac] whichValue = new 
Integer(ModelTest.getMinAIC().getId());
[javac]  ^
[javac] 
/<>/jmodeltest-2.1.10+dfsg/src/main/java/es/uvigo/darwin/jmodeltest/utilities/MyTableCellRenderer.java:57:
 warning: [deprecation] Integer(int) in Integer has been deprecated
[javac] whichValue = new 
Integer(ModelTest.getMinAICc().getId());
[javac]  ^
[javac] 
/<>/jmodeltest-2.1.10+dfsg/src/main/java/es/uvigo/darwin/jmodeltest/utilities/MyTableCellRenderer.java:59:
 warning: [deprecation] Integer(int) in Integer has been deprecated
[javac] whichValue = new 
Integer(ModelTest.getMinBIC().getId());
[javac]  ^
[javac] 
/<>/jmodeltest-2.1.10+dfsg/src/main/java/es/uvigo/darwin/jmodeltest/utilities/MyTableCellRenderer.java:61:
 warning: [deprecation] Integer(int) in Integer has been deprecated
[javac] whichValue = new 
Integer(ModelTest.getMinDT().getId());
[javac]  ^
[javac] 
/<>/jmodeltest-2.1.10+dfsg/src/main/java/es/uvigo/darwin/jmodeltest/utilities/MyTableCellRenderer.java:63:
 warning: [deprecation] Integer(int) in Integer has been deprecated
[javac] whichValue = new Integer(0);
[javac]  ^
[javac] 
/<>/jmodeltest-2.1.10+dfsg/src/main/java/es/uvigo/darwin/jmodeltest/gui/Frame_Progress.java:60:
 warning: [deprecation] Observer in java.util has been deprecated
[javac] public class Frame_Progress extends JModelTestFrame implements 
Observer,
[javac]^
[javac] 
/<>/jmodeltest-2.1.10+dfsg/src/main/java/es/uvigo/darwin/jmodeltest/gui/Frame_Progress.java:368:
 warning: [deprecation] Observable in java.util has been deprecated
[javac] public synchronized void update(Observable o, Object arg) {
[javac] ^
[javac] 
/<>/jmodeltest-2.1.10+dfsg/src/main/java/es/uvigo/darwin/jmodeltest/io/HtmlReporter.java:111:
 warning: [deprecation] Integer(int) in Integer has been deprecated
[javac] datamodel.put("isTopologiesSummary", summary!=null ? 

Bug#915050: (gitlab) Re: Bug#915050: Keep out of testing

[Pirate Praveen]

[adding -devel to cc]

On 12/3/18 8:11 PM, Dominik George wrote:
>> well, Debian is using gitlab!!! so this sentence has no sense. The
>> problem here
>> is that is a complex software that depends of a lot of pieces and it's
>> not
>> easy/possible to fit the definition. So, maybe we should create another
>> category
>> of software.
> 
> Yes, and that Debian officially uses GitLab, from a foreign source, without 
> being able to support it in Debian, does make me feel ashamed for the project.
> 
>> maybe creating another kind of repo. debian-contributuions
>> debian-blabla, whatever.
>>
> 
> We had volatile, which, redefined properly, could help. I am trying to draft 
> such a definition.

Did you get a chance to work on it?

I think it has to be an extension of backports with dependencies that
fall within the backports criteria being maintained in backports and
only packages that cannot be in backports maintained in volatile.

Original definition of volatile from https://www.debian.org/volatile/:
"Some packages aim at fast moving targets, such as spam filtering and
virus scanning, and even when using updated data patterns, they do not
really work for the full time of a stable release. The main goal of
volatile is allowing system administrators to update their systems in a
nice, consistent way, without getting the drawbacks of using unstable,
even without getting the drawbacks for the selected packages. So
debian-volatile will only contain changes to stable programs that are
necessary to keep them functional."

Proposed definition:
"Some packages aim at fast moving targets, such as complex web based
software with very small release cycles and new dependencies, they do
not receive security support or bug fixes for the full time of a stable
release. This means backporting targeted fixes are impossible.  The main
goal of volatile is allowing system administrators to update their
systems in a nice, consistent way, without getting the drawbacks of
using unstable, even without getting the drawbacks for the selected
packages. New dependencies introduced can be maintained in backports
repository. So debian-volatile will be an extension of debian-backports,
with dependencies that fall within the criteria maintained in
debian-backports."





signature.asc
Description: OpenPGP digital signature