Bug#911130: Package doesn't actually bump SOVERSION

[Ondřej Surý]

Package: libtidy5.6
Version: 1:5.6.0-0.1~exp1
Severity: serious

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

when symbols in the library change, you need to actually bump the
SOVERSION/SONAME of the package.  It's not enough and it's wrong
to just change the package name for several reasons:

1. The old and new package must declare Conflicts/Replaces among themselves
2. It's impossible to do proper transition (due to 1)
3. It will break non-packaged software

So, instead of having libtidy5.6 package that contains libtidy.so.5,
you will need to bump the SOVERSION to 6 (it would be best to
coordinate with upstream) and the package would be named libtidy6.
(The naming convention is lib).

I could help with that if you want, but the current approach is wrong,
it will break things and it needs to be fixed before transition is
started.

Thanks,
Ondrej

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

Kernel: Linux 4.17.0-1-amd64 (SMP w/6 CPU cores)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to en_US.UTF-8), LANGUAGE=en_DK.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to 
en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libtidy5.6 depends on:
ii  libc6  2.27-6

libtidy5.6 recommends no packages.

libtidy5.6 suggests no packages.

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEEw2Gx4wKVQ+vGJel9g3Kkd++uWcIFAlvFeNRfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEMz
NjFCMUUzMDI5NTQzRUJDNjI1RTk3RDgzNzJBNDc3RUZBRTU5QzIACgkQg3Kkd++u
WcIkhA/+IazfDUqK1FeEUMx0gpRiZMc4Wlu6QIz/LsmbLlnvSgB8fE4tcplKYZyP
07w4HyrhRSrouEOeSmdROrbpIqQp1dwC7JFgXyh3JaygSf3uNruVc/DKv8RYkYOB
FsgUWhVo2/f0eJ61pW2J0YIEKxmvhBlLB8oXh3G2jrfl5vxjXR+zm6GQmytjGlwX
EL2A5PTSCLdPaqH6IAYeO9ehSrVCwhA3T2XLCYCyfUwKP4VlHh3IzCOZRVFDabv7
2KbvUsPWj8Lrno3ELpCVs0yfVVfJYPqn/HbTZJGDAAp1cbPFf/FlSQA75eAL+OMy
V2j5DYkNWFxqnMe7odlVJ6/UsUXit7L/Tr4A+WbiFuPZwhMPokEvUuVnKDaPOIHN
3fhxbflVzfaqcwxfH2M1y3dJ4xighh2vN1OUv5zNGZSzdFU0GbubS/orYWISqcaG
MEw+EcTQ5JE0s+ppMVDBxXllqokfJ/ohx4iWZBcFxAdsPW2bLGf/W4/fuZjD1lNO
EdqWwG6TteDE9TsHnSghmbeMcYQj+ynHxAJ7ByUt85mpLs0/Z0rUJ78tpsZQwvEb
Oq4uaTEeBr1APhQeQJv9psIsrU9rHewHxc2+8pvJMRihqUvb13+KLanHBxzb8ktw
ibCURP/VR+rG7V64784m+nk/dFtLj0lw9xCq80hbv9vj1sL6RkA=
=esEQ
-END PGP SIGNATURE-

Bug#903698: sphinxbase: build appears broken for multiple python3 versions

[Samuel Thibault]

Samuel Thibault, le ven. 12 oct. 2018 04:12:08 +0200, a ecrit:
> I'm thinking... My chroots have a lib -> usr/lib symlink. Could it be
> that python somehow gets lost between /lib/python* and /usr/lib/python*,
> and dependending on e.g. inode number or directory order, we could have
> one way or the other?
> 
> Right now I have two VMs with almost the same chroot (differences
> notably lie in .pyc files), one works, the other doesn't. When I mount
> the chroot of one on the other, the chroot behavior holds (i.e. the
> failing chroot keeps failing on the VM which produced a working chroot).

This is driving me crazy :)

I have uploaded the VM images on
https://people.debian.org/~sthibault/tmp/fails.img.gz
https://people.debian.org/~sthibault/tmp/works.img.gz

Booting one or the other does not matter. What does matter is the
disk image used to store the chroot. Each VM image has its own
/var/cache/pbuilder/sphinxbase-build directory (almost exactly the
same), and it does not matter which of the two I copy, if I copy it
inside the fails.img disk I'm getting the lintian issue, and if it's
inside the works.img disk I'm not getting it (there's a fresh checkout
of sphinbase in /tmp/sphinxbase inside the chroots). And of course my
own main system is in the fails case, thus preventing me from building
the package :) tune2fsk does not show any difference between the two
filesystem options, just creation time, mount count & such.

Any other idea of what could be different between the two filesystems?

Samuel

Bug#910911: Could there be any databases built by Debian which might be affected.

[shirish शिरीष]

Dear all,

While upgrading my system, I came across this bug (shared by apt-listbugs) .

I wonder if there are any gdbm databases which are built and have that
database.

The one example that was shared by6 Niko was of libmarc-charset-perl
an optional component. Maybe some core packges might be affected
though ?

Also how do I recognize which files or package are vulnerable to this change ?

-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8

Bug#911120: espeakup fails to install

[Samuel Thibault]

Please always keep the bug in Cc, so that I am not the only
recipient of the mail. Writing to me only means risking falling in
the middle of my vacations and thus not getting an answer for weeks,
or that I just don't have the time to answer and thus you would at
best get a terse answer, or worse, no answer at all... Conversely,
keeping the bug in Cc means avoiding all these issues completely,
you'll involve all the community to help you, make the answers you
get available to everyone, and even archived for web crawlers to find
them whenever somebody has the same issue.

Keith Barrett, le lun. 15 oct. 2018 23:34:16 +0100, a ecrit:
> > I.e. just run modprobe speakup_soft before this.
> Right, no joy, unfortunately.
> 
> sudo modprobe speakup_soft
> No error message.
[...]
> espeakup -d
> Unable to open the softsynth device no such file or directory

Does /dev/softsynth exist after that?

If not, what does dmesg tell?

Samuel

Bug#911120: espeakup fails to install

[Keith Barrett]

On 15/10/18 22:02, Samuel Thibault wrote:

Hello,

Keith Barrett, le dim. 14 oct. 2018 16:50:08 +0100, a ecrit:

I removed the package with a view to reinstalling but

invoke-rc.d: initscript espeakup, action "start" failed.


Mmm, perhaps you just need to have the speakup_soft module loaded?

I.e. just run modprobe speakup_soft before this.

Right, no joy, unfortunately.

sudo modprobe speakup_soft
No error message.

sudo apt-get install espeakup
Reading package lists...
Building dependency tree...
Reading state information...
espeakup is already the newest version (1:0.80-10).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] Setting up espeakup (1:0.80-10) ...
update-rc.d: warning: start and stop actions are no longer supported; 
falling back to defaults
Job for espeakup.service failed because the control process exited with 
error code.

See "systemctl status espeakup.service" and "journalctl -xe" for details.
invoke-rc.d: initscript espeakup, action "start" failed.
● espeakup.service - Software speech output for Speakup
   Loaded: loaded 
(#]8;;file://debian/lib/systemd/system/espeakup.service#/lib/systemd/system/espeakup.service#]8;;#; 
enabled; vendor preset: enabled)
   Active: activating (auto-restart) (Result: exit-code) since Mon 
2018-10-15 23:15:52 BST; 17ms ago

 Docs: #]8;;man:espeakup(8)#man:espeakup(8)#]8;;#
  Process: 3089 ExecStart=/usr/bin/espeakup -V ${VOICE} 
#[0;1;31m(code=exited, status=2)#[0m

dpkg: error processing package espeakup (--configure):
 installed espeakup package post-installation script subprocess 
returned error exit status 1

Errors were encountered while processing:
 espeakup
E: Sub-process /usr/bin/dpkg returned an error code (1)
espeakup -d
Unable to open the softsynth device no such file or directory








I'll make espeakup to just load the module itself to avoid that issue.


If that's not the issue, you can try to run espeakup by hand to see
which error shows up:

espeakup -d

Samuel

Bug#911045: xenstore-utils: removal of xenstore-utils makes files disappear from xen-utils-common

[Ian Jackson]

Ian Jackson writes ("Re: xenstore-utils: removal of xenstore-utils makes files 
disappear from xen-utils-common"):
> > The installation sequence to reproduce this problem is
> > 
> >   apt-get install xen-utils-common/stretch
> >   # (1)
> >   apt-get install xenstore-utils/sid
> >   apt-get remove xenstore-utils
> >   # (2)
> 
> But this is not possible because xen-utils-common Depends on
> xenstore-utils (even in stretch).  You could in theory upgrade only
> xenstore-utils and then downgrade it again, to make the files
> disappear, but I don't think that is supported.  And in practice
> no-one would do that.
> 
> So I don't think this is a bug we care about.

Indeed I looked at the log and it does show a downgrade, not a
removal, of xenstore-utils.

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#911045: xenstore-utils: removal of xenstore-utils makes files disappear from xen-utils-common

[Ian Jackson]

> The installation sequence to reproduce this problem is
> 
>   apt-get install xen-utils-common/stretch
>   # (1)
>   apt-get install xenstore-utils/sid
>   apt-get remove xenstore-utils
>   # (2)

But this is not possible because xen-utils-common Depends on
xenstore-utils (even in stretch).  You could in theory upgrade only
xenstore-utils and then downgrade it again, to make the files
disappear, but I don't think that is supported.  And in practice
no-one would do that.

So I don't think this is a bug we care about.

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.

Processed: reassign 911056 to chromium

[Debian Bug Tracking System]

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

> reassign 911056 chromium
Bug #911056 [chromium,webext-browserpass] chromium,webext-browserpass: 
impossible to install chromium and webext-browserpass together
Bug reassigned from package 'chromium,webext-browserpass' to 'chromium'.
Ignoring request to alter found versions of bug #911056 to the same values 
previously set
Ignoring request to alter fixed versions of bug #911056 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#911056: chromium,webext-browserpass: impossible to install chromium and webext-browserpass together

[Michael Meskes]

Unless chromium changed the places it looks for some files, I guess this is an
oversight in chromium and thus be fixed there.

Michael
-- 
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Meskes at (Debian|Postgresql) dot Org
Jabber: michael at xmpp dot meskes dot org
VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL

Processed: merging 911056 911067

[Debian Bug Tracking System]

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

> merge 911056 911067
Bug #911056 [chromium] chromium,webext-browserpass: impossible to install 
chromium and webext-browserpass together
Bug #911056 [chromium] chromium,webext-browserpass: impossible to install 
chromium and webext-browserpass together
Marked as found in versions chromium-browser/70.0.3538.54-1.
Bug #911067 [chromium] chromium: Conflict with chrome-gnome-shell /etc/chromium
Merged 911056 911067
> thanks
Stopping processing here.

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

Processed: your mail

[Debian Bug Tracking System]

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

> forcemerge 899240 909658
Bug #899240 [debian-installer] debian-installer: blank screen on boot (6th Gen. 
ThinkPad X1)
Bug #909658 [debian-installer] debian-installer: blank screen on install (HP 
Elitebook 830 G5)
Severity set to 'normal' from 'serious'
Added tag(s) d-i.
Merged 899240 909658
> severity 899240 serious
Bug #899240 [debian-installer] debian-installer: blank screen on boot (6th Gen. 
ThinkPad X1)
Bug #909658 [debian-installer] debian-installer: blank screen on install (HP 
Elitebook 830 G5)
Severity set to 'serious' from 'normal'
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Processed (with 1 error): Re: Bug#909658: debian-installer: blank screen on install (HP Elitebook 830 G5)

[Debian Bug Tracking System]

Processing control commands:

> merge 899240 -1
Bug #899240 [debian-installer] debian-installer: blank screen on boot (6th Gen. 
ThinkPad X1)
Unable to merge bugs because:
severity of #909658 is 'important' not 'normal'
Failed to merge 899240: Did not alter merged bugs.

> severity -1 serious
Bug #909658 [debian-installer] debian-installer: blank screen on install (HP 
Elitebook 830 G5)
Severity set to 'serious' from 'important'

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

Bug#885051: marked as done (pdfmod: Depends on old GNOME libraries)

[Debian Bug Tracking System]

Your message dated Mon, 15 Oct 2018 22:08:57 +
with message-id 
and subject line Bug#885051: fixed in pdfmod 0.9.1-8.1
has caused the Debian Bug report #885051,
regarding pdfmod: Depends on old GNOME libraries
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.)


-- 
885051: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885051
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pdfmod
Version: 0.9.1-8
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs gconf libgnome
Tags: sid buster
X-Debbugs-CC: hyper...@debian.org

As announced [1], we do not intend to release Debian 10 "Buster" with
the old libgnome (and related) libraries. These libraries have been
deprecated and unmaintained for several years.

Your package depends and or build-depends on these libraries:

- gconf
- libgconf2.0-cil
- libgnome2.24-cil

Please port your package to GTK3 and related maintained libraries.
Otherwise, please consider requesting that your package be removed from
Debian to help us complete this goal.

[1] https://lists.debian.org/debian-devel/2017/10/msg00299.html

On behalf of the Debian GNOME team,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: pdfmod
Source-Version: 0.9.1-8.1

We believe that the bug you reported is fixed in the latest version of
pdfmod, 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.
Jeremy Bicha  (supplier of updated pdfmod 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, 13 Oct 2018 16:43:48 -0400
Source: pdfmod
Binary: pdfmod pdfmod-dbg
Architecture: source
Version: 0.9.1-8.1
Distribution: unstable
Urgency: medium
Maintainer: Debian CLI Applications Team 

Changed-By: Jeremy Bicha 
Description:
 pdfmod - simple tool for modifying PDF documents
 pdfmod-dbg - simple tool for modifying PDF documents -- debugging symbols
Closes: 885051
Changes:
 pdfmod (0.9.1-8.1) unstable; urgency=medium
 .
   * Non-maintainer upload
   * Build-Depend on libgtk2.0-cil-dev instead of libgnome2.0-cil-dev
 (Closes: #885051)
   * Revert commit that added gconf dependency
   * Workaround autoreconf
   * Build with mcs
   * Update Vcs fields for migration to https://salsa.debian.org/
   * Build-Depend on docbook-xml for build tests
   * Update debian/watch and drop obsolete get-orig-source rule
   * Update homepage
   * Add minimal debian/gbp.conf
Checksums-Sha1:
 abcb7bca1f865b4d619ab3956c6ebaff9210cd2d 2209 pdfmod_0.9.1-8.1.dsc
 8979a752e594cf53cc0a95bf7d33979bfa34e86f 9028 pdfmod_0.9.1-8.1.debian.tar.xz
 09c9f40946f6c1c90288684ae0ae92359e5b4aa5 8446 pdfmod_0.9.1-8.1_source.buildinfo
Checksums-Sha256:
 93af010fe2470f7c117bd51f0ec996bff81d01cadf53ac5385812c4ff47a2aa8 2209 
pdfmod_0.9.1-8.1.dsc
 68e1e196b54dbd71df80bf0574f79f1db286bd3d9d062e551e9fb306019a7dc7 9028 
pdfmod_0.9.1-8.1.debian.tar.xz
 9896c4697164cd6ee8de63c5497a1e4d5cbadce59c07919aeb8214653bce23bc 8446 
pdfmod_0.9.1-8.1_source.buildinfo
Files:
 6ff532d39dc43c941cab5928f377a6d5 2209 gnome optional pdfmod_0.9.1-8.1.dsc
 084a55eaa3d0601239a748a36c7b155a 9028 gnome optional 
pdfmod_0.9.1-8.1.debian.tar.xz
 c6c7b590f9bf8cebe67c83e50ca08532 8446 gnome optional 
pdfmod_0.9.1-8.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAlvCYcUACgkQ5mx3Wuv+
bH1EQg/+LCqlSWpyZsgxcB1XJ89bsY1tJGwFfl90bli7mqKeqjQEY5g96KXnZqQA
xUvhGWzwM7sdyrdUQ0FuzddHqydsIU/EOypTIZChtJG3jxKUZA04chQst61xLcmC
LPrlJCeeOcCxTLIOlIgPvohMnn2oYsuyuzcj8wJX7I8A6mQIwLItvRZiN9SMeyGt
07vspT5fMuG9sC+i3/w6iWgExOPsAUFhHmod0PK/RiHd/SIOqkjhlZoFG929rd4D
TA6HVPI7tNFMIodj0BkpKhbYNR+sHFz1t7sY0j404XXYA1B+dLzDq81KPBVWLjQa
Atk2+C5vjoXfJ+ZktKpD75mko0SQd6VriqMhMUgMA8woYhRLEA6uv6h9iGap3bZX
UrQO3B6xdFPrfaX/firZXkFA9IfscLpzh5FfsYu8oNVRV9zPBpgSXu62o8gzUT9y
O+SOEXpdUGlgQQ+hwOtAMyeG2k48dVpgY6SpJaLzgl1TxBnGObHTziBueFrzlUCT
EGqhbX9J6akVAhalg0z0ft7daH7W2snL9+FCFyZMQ0gjV4RBAyjPSx0Yu+Ffo0rk
tcfQz6g7qU/8+zRpe1KrAi58WmS1zdlRW7qoTIbTZnqG4WCUb8TTzoQyR8uDILcj
wnavb3RQ3vf9xgswsZ0yDn9I24fuCpLqegw1sW6WDk0ubbhhzrg=
=T4Bh
-END PGP SIGNATURE End Message ---

Processed: closing 911120

[Debian Bug Tracking System]

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

> close 911120 1:0.80-11
Bug #911120 [espeakup] espeakup: Does not fully install
There is no source info for the package 'espeakup' at version '1:0.80-11' with 
architecture ''
Unable to make a source version for version '1:0.80-11'
Marked as fixed in versions 1:0.80-11.
Bug #911120 [espeakup] espeakup: Does not fully install
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#911120: closing 911120

[Samuel Thibault]

close 911120 1:0.80-11
thanks

Bug#911120: espeakup: Does not fully install

[Keith Barrett]

Package: espeakup
Version: 1:0.80-10
Severity: grave
Tags: a11y
Justification: renders package unusable

Dear Maintainer,

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

   * What led up to the situation?
Frequent loss of speech in the console, particularly when switching to another 
console or from the desktop.
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
Removed the package with a view to reinstalling.

   * What was the outcome of this action?
Package failed to install
   * What outcome did you expect instead?
Package to fully install and work.
*** End of the template - remove these template lines ***


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

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

Versions of packages espeakup depends on:
ii  espeak 1.48.04+dfsg-6
ii  libc6  2.27-6
ii  libespeak-ng1  1.49.2+dfsg-4
ii  lsb-base   9.20170808

espeakup recommends no packages.

espeakup suggests no packages.

-- no debconf information

Bug#910915: marked as done (fenrir: fails to install: SyntaxError)

[Debian Bug Tracking System]

Your message dated Mon, 15 Oct 2018 21:27:33 +
with message-id 
and subject line Bug#910915: fixed in fenrir 1.9.3-2
has caused the Debian Bug report #910915,
regarding fenrir: fails to install: SyntaxError
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.)


-- 
910915: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910915
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fenrir
Version: 1.9.3-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...):

  Selecting previously unselected package fenrir.
  (Reading database ... 
(Reading database ... 5448 files and directories currently installed.)
  Preparing to unpack .../fenrir_1.9.3-1_all.deb ...
  Unpacking fenrir (1.9.3-1) ...
  Setting up fenrir (1.9.3-1) ...
File "/usr/lib/python3/dist-packages/fenrirscreenreader/fenrirVersion.py", 
line 7
  version = 1.9.3
^
  SyntaxError: invalid syntax
  
  dpkg: error processing package fenrir (--configure):
   installed fenrir package post-installation script subprocess returned error 
exit status 1
  Errors were encountered while processing:
   fenrir


cheers,

Andreas


fenrir_1.9.3-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: fenrir
Source-Version: 1.9.3-2

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

Debian distribution maintenance software
pp.
Samuel Thibault  (supplier of updated fenrir package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 15 Oct 2018 23:15:19 +0200
Source: fenrir
Binary: fenrir
Architecture: source
Version: 1.9.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Accessibility Team 
Changed-By: Samuel Thibault 
Description:
 fenrir - Userland console (TTY) screen reader written in python
Closes: 910915
Changes:
 fenrir (1.9.3-2) unstable; urgency=medium
 .
   * debian/patches/bogus_version: Drop bogus version variable
 (Closes: Bug#910915).
Checksums-Sha1:
 6dde719bc1183d396d91c70cc338b77ce5f0e668 1980 fenrir_1.9.3-2.dsc
 1ed09690094de07b0d7111d16a8c5aa5f72893bd 3048 fenrir_1.9.3-2.debian.tar.xz
Checksums-Sha256:
 f8fd4d0dc40ecda85637bc9bb31ee76bef83bfbd3eb80d6ea3583c7c23f988df 1980 
fenrir_1.9.3-2.dsc
 9a32faee213238db4daeab18feaeec8dd62b81037d7691150c358898948c8fc7 3048 
fenrir_1.9.3-2.debian.tar.xz
Files:
 f250fe9d365adabfd2f013c80349342c 1980 admin optional fenrir_1.9.3-2.dsc
 21115e1353987b4c33fa5b90d7613761 3048 admin optional 
fenrir_1.9.3-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOjpdRkZg6GdhDKQnmWhJwc9WBHgFAlvFA8YACgkQmWhJwc9W
BHiurA//eMzf+aOqd/OUFy24KoJqbWsVsOVrE00Heley77EYFgS13l2xgQMdxrM+
wSGD/+gUxz/fGHoGUYglkzDGEJTWxhwjOQ1wcJpKk+myE2wBn8yPsSJMbf+gbjhl
ChM7h6MfGyydq+4JvT9y2FraIdG1bt1tq4PK5NN9O/seisx6h1QTTvKQN7x6yIFL
IxnEN0d0JUqAvwrzW4UcumwJgX8QX2H8fKmFQNvOCQ16ONigC+356OfvslkvajZ9
wqH4t9QXix42uGw9cd+CbRJzOA2vtz2PLA53/67YgxaEZOYm1EwN1Dpk5FlxiDCj
HoBNio0SXD0UodO+flXfp8k6/soyJWbEkG+h0bX1PAjNdncJANDO9N+onuqtQCvX
gQFmYeRdrniBlIrPTM0SBnUKyGR2VldQKkpPBzfo2tqV5NCGhlhSaivgQSbPhVCC
+RZTNzhWqR+p1AybdQXRZBCgbKMvBK/9ntlC4XxXkO1pSAubLKspvkEkNr1ykJRH
LIizKQyKdm0IrPcxPKeiOs1turJmwj469wn+JHxt/2y4SFB7sBl4WQssaQ7XWahT
ft2zM1O3YHGu+E+hU95oR/FtuDSz/NImkd25c2A0nQCE30VUI7pIv9qZxVmRRqGF
f6k8k8gTmIuPcUa9MMbRepdCvcw6IMrIas9GIo9iebAQBdoEaU0=
=h3SR
-END PGP SIGNATURE End Message ---

Bug#885672: marked as done (cellwriter: Unnecessary Build-Depend on libgnome)

[Debian Bug Tracking System]

Your message dated Mon, 15 Oct 2018 21:26:28 +
with message-id 
and subject line Bug#885672: fixed in cellwriter 1.3.6-1
has caused the Debian Bug report #885672,
regarding cellwriter: Unnecessary Build-Depend on libgnome
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.)


-- 
885672: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885672
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cellwriter
Version: 1.3.5-1
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs libgnome
Tags: sid buster patch

As announced [1], we do not intend to release Debian 10 "Buster" with
the old libgnome (and related) libraries. These libraries have been
deprecated and unmaintained for several years.

Your package appears to have an unnecessary Build-Depends on libgnome2-
dev. (No patch attached because this is pretty trivial to fix.)

[1] https://lists.debian.org/debian-devel/2017/10/msg00299.html

On behalf of the Debian GNOME team,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: cellwriter
Source-Version: 1.3.6-1

We believe that the bug you reported is fixed in the latest version of
cellwriter, 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.
Jeremy Bicha  (supplier of updated cellwriter package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 15 Oct 2018 16:04:11 -0400
Source: cellwriter
Binary: cellwriter
Architecture: source
Version: 1.3.6-1
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Jeremy Bicha 
Description:
 cellwriter - grid-entry handwriting input panel
Closes: 885672
Changes:
 cellwriter (1.3.6-1) unstable; urgency=medium
 .
   * QA upload.
   * Orphan package. See #93
   * Drop unused Build-Depends on libgnome2-dev (Closes: #885672)
   * New upstream release
   * Update watchfile and homepage
   * Update Vcs fields for migration to https://salsa.debian.org/
   * Add minimal debian/gbp.conf
   * Bump debhelper compat to 11
   * Drop obsolete debian/menu
   * Bump Standards-Version to 4.2.1
   * Skip running dh_auto_clean because of problems with the tarball
Checksums-Sha1:
 bfe62016e0d0aa0136dcfa72ea85ef3c24bedfe5 1885 cellwriter_1.3.6-1.dsc
 ef170d15ffe57138ecf129c9ff1a672a80baab3d 434211 cellwriter_1.3.6.orig.tar.gz
 deff5ed1b61b6842b38fc9f6e7477d0eafd35cab 3024 cellwriter_1.3.6-1.debian.tar.xz
 2f3cf0ebe2d4792cfd73bc9b347425f52b3b61b5 7688 
cellwriter_1.3.6-1_source.buildinfo
Checksums-Sha256:
 b4872a1d30e8ac12cd0db8b664b52eb32eafa8f953230d176e136d9172edd609 1885 
cellwriter_1.3.6-1.dsc
 17bb07226d4680b565b18a60494cb19cdf9067b427c8df7454c16d809de9963b 434211 
cellwriter_1.3.6.orig.tar.gz
 4ec16a56dae7d254e5531d31c223a2af9c7841d2d84ab7985398eddb2357d7bf 3024 
cellwriter_1.3.6-1.debian.tar.xz
 7653f602cdadf517ba8dcb0b7898df8e972a6d41e0b78fea016c3fa9bca29604 7688 
cellwriter_1.3.6-1_source.buildinfo
Files:
 34847d1c07d7711f0355982ed4a97258 1885 gnome optional cellwriter_1.3.6-1.dsc
 826de84d6d9f00a9c25e892986287f58 434211 gnome optional 
cellwriter_1.3.6.orig.tar.gz
 ccfa8474a135b8ead64526571fa7435e 3024 gnome optional 
cellwriter_1.3.6-1.debian.tar.xz
 b511d4453f5dc98e3228655b1edd0f00 7688 gnome optional 
cellwriter_1.3.6-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAlvE8wkACgkQ5mx3Wuv+
bH1wvA/+K0QzGBn9yYfFms19wXHERZpP7UnlgEKpK8WvEpKc2W7vihNjgoby1NZ2
R8lbo9dqgrcuSSWcJDCCVaONh3AwxOQRGHdi8vi0kfklm1j8o5FmJba8BwVwx0T4
vR25haVcyW2vCXD+AVvW5s+G2alonh6CTqFW2s08BriPZF44UtyOZRjmA9vqUtVL
axkvkp8stjOuJ2Pyj5QYEJcKuSpl9aBGd8gwZ+ze+Xm9iYhDZl8HvC+eP4FgfV8A
AdA/6wGm34D+sklf7MujRyJY2DcXV+opoLY/S0G0GQDesKdlPepRdjW/Ox0VGPkd
UcwdMO8/tuCVYe7Ru5Da3tmqo2QaKUnBlHgQHc6hiTw2qeGXGBU+cFS67P6KtVK6
PlLCAumUGDWOICxgxoZ5kBGh6RnGaaQzMddMJ2oXv02o9GLNhkgJhamcgdrQ29Q1
5WrrGuPPTMQz8oj4o6NmiyUVBMPBlAHZ+Hdoojn3FzUwoRhhKeTeAeJU49Xwif28
EfE5aRPunRdpmb/nL73nYGBfvCAXkwhmpZPBIrDssm2P2gY8wy63qtOiG8yedhNE
0omPJoKp0JZbzvlAu4dMNGAJDj2W59m0h1WHZHW/ctYvmk8liGwL14f1SAII8bkg
zaVdgLBxRgcEYx0IMV+oaay61mTANxfGcfx6S1iVc5Bk0VKnlRQ=
=Qr74
-END PGP 

Processed: tagging 910915

[Debian Bug Tracking System]

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

> tags 910915 + pending
Bug #910915 [fenrir] fenrir: fails to install: SyntaxError
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#868411: gniall: Port to GTK+ 3

[Jeremy Bicha]

On Mon, Oct 15, 2018 at 3:59 PM Yavor Doganov  wrote:
> It would be great if you can create a repository (possibly using gbp's
> --debsnap option), import it at Salsa and grant me commit access.
> That way, I can make gradual commits which will be easier to review by
> a potential sponsor (rather than a giant debdiff).

I created an empty Salsa repo at https://salsa.debian.org/debian/gniall

Go ahead and push your packaging there. I can sponsor directly from
the git repo, so ping me when you're ready for upload.

The orphan bug is https://bugs.debian.org/97

Thanks,
Jeremy

Bug#909000: Thunderbird 60 cannot STILL be at stretch normal repository

[Jonas Meurer]

Hello,

On Wed, 10 Oct 2018 19:19:53 +0200 Narcis Garcia 
wrote:
> Stable packages aren't ready for Thunderbird 60 presence.
> It's better to wait for better repository consistence before adding this
> update.

With keeping Thunderbird at version 52 in stretch you mean to keep the
packages with known security vulnerabilites? For obvious reasons, that's
not an option.

Cheers
 jonas



signature.asc
Description: OpenPGP digital signature

Bug#868382: gbatnav: Please drop the (build-)dependency against gnome-vfs

[Jeremy Bicha]

Ying-Chun Liu, please review the patch attached to
https://bugs.debian.org/868382 to fix the RC bug keeping gbatnav out
of Testing. If we don't hear from you soon, we will NMU this package.

Thanks,
Jeremy Bicha

Bug#868411: gniall: Port to GTK+ 3

[Yavor Doganov]

Jeremy Bicha wrote:
> Yavor, I'm planning to orphan gniall now. Are you interested in being
> its maintainer in Debian? It's ok if you don't want to.

No, but if it gets orphaned, I can prepare a QA upload fixing other
packaging issues and take care of it in the future (I'm already
subscribed to the PTS), treating it like my own package.  This is more
or less the same thing as adopting it.

It would be great if you can create a repository (possibly using gbp's
--debsnap option), import it at Salsa and grant me commit access.
That way, I can make gradual commits which will be easier to review by
a potential sponsor (rather than a giant debdiff).

Bug#910395: mediathekview with openjfx 11

[Markus Koschany]

Hi,

Am 15.10.18 um 19:45 schrieb Erich Schubert:
> Hi,
> 
> It seems the classpath is not set up correctly.
> 
> With Java 11 as my main java, the following works:
> 
> java -cp
> /usr/share/mediathekview/MediathekView.jar:/usr/share/java/javafx-base-11.jar:/usr/share/java/javafx-controls-11.jar:/usr/share/java/javafx-fxml-11.jar:/usr/share/java/javafx-graphics-11.jar:/usr/share/java/javafx-media-11.jar:/usr/share/java/javafx-swing-11.jar:/usr/share/java/javafx-web-11.jar
> mediathek.Main
> 
> Since this launches correctly (I haven't tried to load anything though)
> it seems the classpath / launch script is the problem.
> 
> (If your default java is 8, you may need to set JAVA_HOME or use the
> full path name).

How could you launch mediathekview like that without getting the error
message that JavaFX couldn't be found on the classpath (because you are
using Java 11 and mediathekview checks explicitly for Java 8) ?

I am aware that the javajfx-*.jar files have to be added to the
CLASSPATH now. My problem is that I have to compile with OpenJDK 10 at
the moment and due to some removed class files in this version, I have
to switch to Java 9 bytecode at least. I have also upgraded
Mediathekview to the latest upstream version 13.1.2. I am able to
compile it but I get a RunTimeException with Java 10 or Java 11 and
OpenJFX 11. That is bug #910764.




signature.asc
Description: OpenPGP digital signature

Processed: [bts-link] source package src:xiphos

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:xiphos
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #866657 (http://bugs.debian.org/866657)
> # Bug title: xiphos: depends on libwebkitgtk-3.0-0 which is deprecated
> #  * https://github.com/crosswire/xiphos/issues/794
> #  * remote status changed: closed -> open
> #  * reopen upstream
> tags 866657 - fixed-upstream
Bug #866657 [src:xiphos] xiphos: depends on libwebkitgtk-3.0-0 which is 
deprecated
Removed tag(s) fixed-upstream.
> usertags 866657 - status-closed
Usertags were: status-closed.
Usertags are now: .
> usertags 866657 + status-open
There were no usertags set.
Usertags are now: status-open.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package meson

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package meson
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #910443 (http://bugs.debian.org/910443)
> # Bug title: gir-to-d FTBFS: Error: Expected argument to '-I'
> #  * https://github.com/mesonbuild/meson/pull/4342
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 910443 + fixed-upstream
Bug #910443 [meson] gir-to-d FTBFS: Error: Expected argument to '-I'
Added tag(s) fixed-upstream.
> usertags 910443 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 910443 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Bug#868411: gniall: Port to GTK+ 3

[Jeremy Bicha]

Yavor, I'm planning to orphan gniall now. Are you interested in being
its maintainer in Debian? It's ok if you don't want to.

Thanks,
Jeremy

Bug#911025: Transition to postgresql-11

[Jeremy Bicha]

On Mon, Oct 15, 2018 at 4:30 AM Christoph Berg  wrote:
> Can I help with the transition?

If you want, you can investigate why the build tests seem to hang with
postgresql 11.

You can check whether glom works with postgresql 11.

And you can report any issues to https://gitlab.gnome.org/GNOME/glom/issues
(I don't know if @murrayc is watching that yet so you may want to CC
him there just to be sure he sees issues or merge requests you send.)

I don't really use glom myself. I just added it to Debian since it was
already in Ubuntu and people wanted it.

Thanks,
Jeremy Bicha

Bug#911025: Transition to postgresql-11

[Christoph Berg]

Re: To Jeremy Bicha 2018-10-15 <20181015083032.gb6...@msg.df7cb.de>
> Re: Jeremy Bicha 2018-10-15 
> 
> > How soon do you need this issue fixed? I'm ok with glom being removed
> > from Testing if that helps.
> 
> At the moment the biggest blocker is that llvm-toolchain-7 is not in
> testing (OOM when stripping on mips(el)), so it's not urgent anyway.
> But that could change anytime.

I totally forgot to mention: as we have both pg10 and pg11 as source
packages, reverse-dependencies still depending on pg10 won't block the
transition to testing, so this isn't blocking anything.

> Can I help with the transition?

(That still stands.)

Christoph

Bug#903780: marked as done (gitlab: fails to install: Could not find gem 'fog-google (~> 0.5)')

[Debian Bug Tracking System]

Your message dated Mon, 15 Oct 2018 23:54:39 +0530
with message-id 
and subject line closing
has caused the Debian Bug report #903780,
regarding gitlab: fails to install: Could not find gem 'fog-google (~> 0.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.)


-- 
903780: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903780
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gitlab
Version: 10.6.5+dfsg-2
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 gitlab.
  (Reading database ... 
(Reading database ... 43843 files and directories currently installed.)
  Preparing to unpack .../gitlab_10.6.5+dfsg-2_all.deb ...
  Unpacking gitlab (10.6.5+dfsg-2) ...
  Setting up gitlab (10.6.5+dfsg-2) ...
  Creating/updating gitlab user account...
  adduser: Warning: The home directory `/var/lib/gitlab' does not belong to the 
user you are currently creating.
  Making gitlab owner of /var/lib/gitlab...
  [ESC][31mCould not find gem 'fog-google (~> 0.5)' in any of the gem sources 
listed in
  your Gemfile.[ESC][0m
  dpkg: error processing package gitlab (--configure):
   installed gitlab package post-installation script subprocess returned error 
exit status 1
  Errors were encountered while processing:
   gitlab


cheers,

Andreas


gitlab_10.6.5+dfsg-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
this is already fixed



signature.asc
Description: OpenPGP digital signature
--- End Message ---

Bug#910485: Confirm issue with libpsm2-2/11.2.68-1

[Lippuner, Jonas]

I'm having the same issue with libpsm2-2 version 11.2.68-1. Downgrading
to 10.3.58-2 fixes it for me.


-- 
Jonas Lippuner, PhD
Scientist
Computational Physics and Methods, CCS-2
Center for Theoretical Astrophysics
Los Alamos National Laboratory
jlippu...@lanl.gov
505-667-1646
http://jonaslippuner.com

Bug#911103: android-platform-dalvik: libandroid-dex-java dependency is no longer built

[Jeremy Bicha]

Source: android-platform-dalvik
Version: 7.0.0+r33-1
Severity: serious
X-Debbugs-CC: saif...@cse.mrt.ac.lk

android-platform-dalvik depends and build-dpeends on
libandroid-dex-java but that package is no longer built by
android-platform-libcore.

This has led to android-sdk-meta being removed from Testing.

The libcore update said:
"Remove `libandroid-dex-java`: Sources are moved to `android-platform-dalvik`"

Thanks,
Jeremy Bicha

Bug#910911: libgdbm6: can't read (some?) older GDBM databases

[Dmitry Bogatov]

[2018-10-15 20:18] Niko Tyni 
> > I am sorry to say it, but probably binNMU or sourceful upload would
> > be required for all packages, that bundle gdbm databases, generated
> > by (gdbm << 1.9)
> 
> This sounds really sad. So even the gdbm we have in our current stable
> release is too old to be supported anymore!
> 
> Any packaged databases are easily rebuilt, but what about local user
> databases? I think breaking compat with those is horrible, and I don't
> even see a way to recover their contents after they've upgraded gdbm.

Well, you can use gdbm_dump/stable. What else?

 * I can write debian/NEWS to warn about incompatibility.
 * We can introduce new source package, that provides gdbmtool
   out of gdbm-1.8 (I am not fan of this idea)

Bug#910395: mediathekview with openjfx 11

[Erich Schubert]

Hi,

It seems the classpath is not set up correctly.

With Java 11 as my main java, the following works:

java -cp 
/usr/share/mediathekview/MediathekView.jar:/usr/share/java/javafx-base-11.jar:/usr/share/java/javafx-controls-11.jar:/usr/share/java/javafx-fxml-11.jar:/usr/share/java/javafx-graphics-11.jar:/usr/share/java/javafx-media-11.jar:/usr/share/java/javafx-swing-11.jar:/usr/share/java/javafx-web-11.jar 
mediathek.Main


Since this launches correctly (I haven't tried to load anything though) 
it seems the classpath / launch script is the problem.


(If your default java is 8, you may need to set JAVA_HOME or use the 
full path name).

Bug#911084: sagemath crashes as cantor backend

[Tobias Hansen]

Control: reassign -1 cantor-backend-sage

Please provide more information. How can the bug be triggered? I'm not familiar 
with cantor. If someone can demonstrate that the segfault is really in sage, 
the bug can be reassigned to sagemath.

Best,
Tobias

On 10/15/2018 03:34 PM, Kinky Nekoboi wrote:
> Package: sagemath
> Version: 8.3-3
> Severity: serious
> Justification: unkown
>
> as above
> cantor-sage-backend crashes with Segmentation fault.
>
>
>
> -- System Information:
> Debian Release: buster/sid
>   APT prefers testing
>   APT policy: (500, 'testing')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 4.18.0-2-amd64 (SMP w/2 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 sagemath depends on:
> ii  cysignals-tools  1.6.7+ds-4
> ii  cython   0.28.4-1
> ii  ecl  16.1.2-4+b1
> ii  eclib-tools  20171002-1+b3
> ii  f2c  20160102-1
> ii  fflas-ffpack 2.3.2-3
> ii  flintqs  1:1.0-3
> ii  gap-core 4r8p8-3
> ii  gfan 0.6.2-2
> ii  gmp-ecm  7.0.4+ds-3
> ii  ipython  5.5.0-1
> ii  iso-codes4.1-1
> ii  jmol 14.6.4+2016.11.05+dfsg1-3.1
> ii  lcalc1.23+dfsg-7
> ii  less 487-0.1+b1
> ii  libatlas3-base [liblapack.so.3]  3.10.3-7+b1
> ii  libblas3 [libblas.so.3]  3.8.0-1+b1
> ii  libbrial-groebner3   1.2.0-2
> ii  libbrial31.2.0-2
> ii  libc62.27-6
> ii  libcdd-tools 094h-1+b1
> ii  libcliquer1  1.21-2
> ii  libec3   20171002-1+b3
> ii  libecm1  7.0.4+ds-3
> ii  libflint-2.5.2   2.5.2-18
> ii  libflint-arb21:2.14.0-4
> ii  libgap-sage-4
> 4.8.8+3+20160327g69a66f0+dsx-1
> ii  libgcc1  1:8.2.0-7
> ii  libgd3   2.2.5-4
> ii  libgivaro9   4.0.4-2
> ii  libglpk404.65-2
> ii  libgmp10 2:6.1.2+dfsg-3
> ii  libgmpxx4ldbl2:6.1.2+dfsg-3
> ii  libgsl23 2.5+dfsg-5
> ii  libgslcblas0 2.5+dfsg-5
> ii  libiml0  1.0.4-1+b2
> ii  libjs-mathjax2.7.4+dfsg-1
> ii  libjs-three  80+dfsg2-2
> ii  liblapack3 [liblapack.so.3]  3.8.0-1+b1
> ii  liblfunction01.23+dfsg-7
> ii  liblinbox-1.5.2-01.5.2-2
> ii  liblinboxsage-1.5.2-01.5.2-2
> ii  liblrcalc1   1.2-2+b1
> ii  libm4ri-0.0.20140914 20140914-2+b1
> ii  libm4rie-0.0.2015090820150908-2
> ii  libmpc3  1.1.0-1
> ii  libmpfi0 1.5.3+ds-2
> ii  libmpfr6 4.0.1-1
> ii  libntl35 10.5.0-2
> ii  libopenblas-base [liblapack.so.3]0.3.3+ds-1
> ii  libpari-gmp-tls6 2.11.0-1
> ii  libplanarity03.0.0.5-3
> ii  libpng16-16  1.6.34-2
> ii  libppl14 1:1.2-3
> ii  libpynac18   0.7.22-3
> ii  libratpoints-2.1.3   1:2.1.3-1+b2
> ii  libreadline7 7.0-5
> ii  librw0   0.8+ds-1
> ii  libsingular4 1:4.1.1-p2+ds-2
> ii  libstdc++6   8.2.0-7
> ii  libsymmetrica2   2.0+ds-5
> ii  libzn-poly-0.9   0.9-3+b2
> ii  maxima-sage  5.41.0+ds-2
> ii  maxima-sage-doc  5.41.0+ds-2
> ii  maxima-sage-share5.41.0+ds-2
> ii  nauty2.6r10+ds-1
> ii  octave 

Processed: Re: Bug#911084: sagemath crashes as cantor backend

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 cantor-backend-sage
Bug #911084 [sagemath] sagemath crashes as cantor backend
Bug reassigned from package 'sagemath' to 'cantor-backend-sage'.
No longer marked as found in versions sagemath/8.3-3.
Ignoring request to alter fixed versions of bug #911084 to the same values 
previously set

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

Bug#873156: marked as done (fofix: FoFiX.py rises a NotImplementedError on startup)

[Debian Bug Tracking System]

Your message dated Mon, 15 Oct 2018 17:34:12 +
with message-id 
and subject line Bug#873156: fixed in fofix-dfsg 3.121-5
has caused the Debian Bug report #873156,
regarding fofix: FoFiX.py rises a NotImplementedError on startup
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.)


-- 
873156: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873156
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fofix
Version: 3.121-4
Severity: important
Tags: patch

Dear Maintainer,
after installing the fofix package on a (up-to-date) system, 
the application terminates due to unhandlet exception.
This is caused by the usage of the removed 'tostring()' within python and 
python suggests 'tobytes()' should be used instead. 

After replacing the tostring() calls with tobytes() as suggested, 
the application becomes usable.

I have attached a diff at the end of the report.

kind regards
Christian


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

Kernel: Linux 4.11.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=de_AT.utf8, LC_CTYPE=de_AT.utf8 (charmap=UTF-8), LANGUAGE=de_AT:de 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages fofix depends on:
ii  python  2.7.13-2
ii  python-imaging  4.2.1-1
ii  python-numpy1:1.12.1-3+b2
ii  python-opengl   3.1.0+dfsg-1
ii  python-pygame   1.9.1release+dfsg-10+b2

Versions of packages fofix recommends:
ii  python-ogg   1.3+repack-7
ii  python-pyaudio   0.2.11-1+b1
ii  python-pyvorbis  1.5-4

Versions of packages fofix suggests:
pn  python-psyco  

-- no debconf information

-- Diff after patching:

30c30
< 
---
> 
77c77
<   string = image.tostring('raw', 'RGBA', 0, -1)
---
>   string = image.tobytes('raw', 'RGBA', 0, -1)
80c80
<   string = image.tostring('raw', 'RGB', 0, -1)
---
>   string = image.tobytes('raw', 'RGB', 0, -1)
83c83
<   string = image.tostring('raw', 'L', 0, -1)
---
>   string = image.tobytes('raw', 'L', 0, -1)
89c89
< string = image.tostring('raw', 'RGB', 0, -1)
---
> string = image.tobytes('raw', 'RGB', 0, -1)
114c114
<   string = pygame.image.tostring(surface, "RGB")
---
>   string = pygame.image.tobytes(surface, "RGB")
116c116
<   string = image.tostring('raw', 'L', 0, -1)
---
>   string = image.tobytes('raw', 'L', 0, -1)
120c120
< string = pygame.image.tostring(surface, "RGBA", True)
---
> string = pygame.image.tobytes(surface, "RGBA", True)
123c123
< string = pygame.image.tostring(surface, "RGB", True)
---
> string = pygame.image.tobytes(surface, "RGB", True)
--- End Message ---
--- Begin Message ---
Source: fofix-dfsg
Source-Version: 3.121-5

We believe that the bug you reported is fixed in the latest version of
fofix-dfsg, 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.
Andreas Beckmann  (supplier of updated fofix-dfsg package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 15 Oct 2018 18:25:19 +0200
Source: fofix-dfsg
Binary: fofix
Architecture: source
Version: 3.121-5
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Andreas Beckmann 
Description:
 fofix  - rhythm game in the style of Rock Band(tm) and Guitar Hero(tm)
Closes: 873156
Changes:
 fofix-dfsg (3.121-5) unstable; urgency=medium
 .
   * QA upload.
   * Call image.tobytes('raw', ...) instead of image.tostring('raw', ...),
 thanks to Christian Trenkwalder.  (Closes: #873156)
   * Override source-contains-prebuilt-ms-help-file.
Checksums-Sha1:
 3cdcc8964e0546b77e7099b0a79e0f09e56ab210 1768 fofix-dfsg_3.121-5.dsc
 2179f67fe19d5c7c6a0ef78bac36e6e51797c182 6420 fofix-dfsg_3.121-5.debian.tar.xz
 41814bf49d4f2de1a2738c37e03a309766e8c7b7 5964 
fofix-dfsg_3.121-5_source.buildinfo
Checksums-Sha256:
 1698cdcb8f29afc856399bdd523c2df771e165d218cdc599fcf58155846c4688 1768 
fofix-dfsg_3.121-5.dsc
 

Bug#910911: libgdbm6: can't read (some?) older GDBM databases

[Niko Tyni]

On Mon, Oct 15, 2018 at 12:21:16AM +, Dmitry Bogatov wrote:
> 
> [2018-10-13 13:20] Niko Tyni 
> > The libgdbm6 transition broke autopkgtest checks of src:perl and
> > libmarc-charset-perl.
> > 
> > It looks like some GDBM databases which were working with the older
> > gdbm are not readable any more with the new one.
> 
> After a bit more research I deduced, that libmarc-charset-perl, as
> present in sid, was build with gdbm-1.8.3. gdbm-1.9 is incompatible with
> 1.8.3, so it is pure luck, that thigs worked with gdbm-1.14.
> 
> I am sorry to say it, but probably binNMU or sourceful upload would be
> required for all packages, that bundle gdbm databases, generated by
> (gdbm << 1.9)

This sounds really sad. So even the gdbm we have in our current stable
release is too old to be supported anymore!

Any packaged databases are easily rebuilt, but what about local user
databases? I think breaking compat with those is horrible, and I don't
even see a way to recover their contents after they've upgraded gdbm.

 $ gdbmtool stretch.gdbm recover
 gdbmtool: argv:1.1-8: cannot open database stretch.gdbm: Malformed database 
file header

-- 
Niko Tyni   nt...@debian.org

Bug#899060: FTBFS: even if tests pass, dh_auto_test fails

[Sunil Mohan Adapa]

Hello,

FreedomBox is set to be autoremoved from testing on 2018/10/21 (in about
5 days) due to mod-gnutls which won't transition into testing which in
turn due won't migrate to testing due to its dependency on moneysphere.
This effects all FreedomBox users.

Please consider uploading the monkeysphere package immediately.

Thanks,

-- 
Sunil



signature.asc
Description: OpenPGP digital signature

Bug#868411: gniall: Port to GTK+ 3

[Jeremy Bicha]

On Mon, Oct 15, 2018 at 12:27 PM Yavor Doganov  wrote:
>
> Jeremy Bicha wrote:
> > On Mon, Oct 15, 2018 at 9:13 AM Yavor Doganov  wrote:
> > > Please do what you think is best.
> >
> > No. I'm delegating this decision to you. There is no upstream. There
> > is no Debian maintainer. You're the closest we have to either one of
> > those for this package.
>
> If your question is whether I would deal with future bug
> reports/regressions/etc if the package stays in Debian, then yes, I
> would, to the best of my ability.

Ok, that's good enough for me. I'll look into sponsoring this update for you.

> BTW, if the Debian maintainer is MIA, why this package is not
> orphaned?

The maintainer is still active in Debian (in fact, he's CC'd on these
emails!) but just hasn't gotten around to orphaning the package.

> > By creating these patches, you are making a statement that you believe
> > these apps are worth saving.
>
> How does that follow?  It would never occur to me that I'm making a
> statement.  There's an RC bug, my intention is to fix it.  I check if
> there's an RM bug or intention to file an RM bug, I check if the bug
> is not already fixed upstream and if these are false, I start working
> on it.  Evaluating whether it's worth to save the package or kick it
> out is sometimes more complex than fixing the bug, furthermore I don't
> think I'm qualified to make such evaluations.
>
> > Otherwise, I or someone else would eventually file removal bugs for
> > all these packages.
>
> Right, ideally shortly after filing the RC bugs (or raising the
> severity) so that people don't lose time to fix RC bugs that are going
> to be "fixed" by RMing the package.

An RC bug alone isn't quite enough justification to remove a package
and would make some maintainers upset. (It's a nuisance having to get
packages through the NEW queue again once they've been removed from
Debian.)

We can remove packages once there has been sufficient time and notice
to the maintainer that the package will be removed unless the
maintainer objects (or unless someone like you fixes the bug!). I have
started filing bugs like https://bugs.debian.org/910957 and
https://bugs.debian.org/893861 to provide that time and notice. (There
are some packages where I have contacted the maintainer privately via
email to inquire about removing the package but the bug report may be
better) I have completed many removals as part of this libgnome
cleanup.

I would have filed several more intent to remove bugs but I see that
you have very recently posted patches for several packages I was
looking at. We can NMU those, but let's see if the maintainers respond
to your patches first.

Thanks,
Jeremy Bicha

Bug#911067: chromium: Conflict with chrome-gnome-shell /etc/chromium

[Modestas Vainius]

Hello,

2018 m. spalio 15 d., pirmadienis 16:11:38 EEST Patrick Franz rašė:
> > 
> > dpkg: erreur de traitement de l'archive /var/cache/apt/archives/
> 
> chromium_70.0.3538.54-2_amd64.deb (--unpack) :
> >  tentative de remplacement du répertoire « /etc/chromium » dans le
> 
> paquet chrome-gnome-shell 10.1-1 avec un élément de type différent
> 
> In my case, it conflicts with plasma-browser-integration, but I think
> it's the same error:
> 
> dpkg: Fehler beim Bearbeiten des Archivs /var/cache/apt/archives/
> chromium_70.0.3538.54-2_amd64.deb (--unpack):
>  Versuch, Verzeichnis »/etc/chromium« in Paket plasma-browser-
> integration 5.13.5-1 mit Nichtverzeichnis zu überschreiben
> 
> 
> Essentially it says, that it tries to override /etc/chromium in the
> package plasma-browser-integration with a "non-directory".

Since they ship native message hosts which are configured via /etc/chromium/
native-messaging-hosts/*.json according to https://developer.chrome.com/apps/
nativeMessaging

I guess the change should be reverted as other location would conflict with 
official documentation ...

Bug#868411: gniall: Port to GTK+ 3

[Yavor Doganov]

Jeremy Bicha wrote:
> On Mon, Oct 15, 2018 at 9:13 AM Yavor Doganov  wrote:
> > Please do what you think is best.
> 
> No. I'm delegating this decision to you. There is no upstream. There
> is no Debian maintainer. You're the closest we have to either one of
> those for this package.

If your question is whether I would deal with future bug
reports/regressions/etc if the package stays in Debian, then yes, I
would, to the best of my ability.

BTW, if the Debian maintainer is MIA, why this package is not
orphaned?

> By creating these patches, you are making a statement that you believe
> these apps are worth saving.

How does that follow?  It would never occur to me that I'm making a
statement.  There's an RC bug, my intention is to fix it.  I check if
there's an RM bug or intention to file an RM bug, I check if the bug
is not already fixed upstream and if these are false, I start working
on it.  Evaluating whether it's worth to save the package or kick it
out is sometimes more complex than fixing the bug, furthermore I don't
think I'm qualified to make such evaluations.

> Otherwise, I or someone else would eventually file removal bugs for
> all these packages.

Right, ideally shortly after filing the RC bugs (or raising the
severity) so that people don't lose time to fix RC bugs that are going
to be "fixed" by RMing the package.

Bug#899594: marked as done (lirc-compat-remotes: Invalid maintainer address pkg-lirc-ma...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Mon, 15 Oct 2018 16:21:49 +
with message-id 
and subject line Bug#899594: fixed in lirc-compat-remotes 0.9.0-1.1
has caused the Debian Bug report #899594,
regarding lirc-compat-remotes: Invalid maintainer address 
pkg-lirc-ma...@lists.alioth.debian.org
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.)


-- 
899594: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899594
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:lirc-compat-remotes
Version: 0.9.0-1
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of lirc-compat-remotes,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package lirc-compat-remotes since the list address
pkg-lirc-ma...@lists.alioth.debian.org used in the Maintainer: field
was not transferred to the alioth-lists service that provides a
continuation for the lists in the @lists.alioth.debian.org domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
pkg-lirc-ma...@lists.alioth.debian.org is 4.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: lirc-compat-remotes
Source-Version: 0.9.0-1.1

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

Debian distribution maintenance software
pp.
Gianfranco Costamagna  (supplier of updated 
lirc-compat-remotes package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 15 Oct 2018 18:09:09 +0200
Source: lirc-compat-remotes
Binary: lirc-compat-remotes
Architecture: source
Version: 0.9.0-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Lirc Team 
Changed-By: Gianfranco Costamagna 
Description:
 lirc-compat-remotes - Compatibility remote definitions for lirc
Closes: 899594
Changes:
 lirc-compat-remotes (0.9.0-1.1) unstable; urgency=medium
 .
   * NMU upload
   * Update maintainer field (Closes: #899594)
Checksums-Sha1:
 466ea5b93706f8d307f01e58e8058dddbb037aab 1868 lirc-compat-remotes_0.9.0-1.1.dsc
 ea9ad9902d5526f8e9cda68415b6b1b95dbb1e3f 1768 
lirc-compat-remotes_0.9.0-1.1.debian.tar.xz
 32f6877398cec336992242aa9c3c7c12cd368224 6669 
lirc-compat-remotes_0.9.0-1.1_source.buildinfo
Checksums-Sha256:
 b1e24a4233a2b80d215f94f622df1a66e026c5959a91c8d4e756c6163dc2a645 1868 
lirc-compat-remotes_0.9.0-1.1.dsc
 7132d306b72db60caba79f23480b6750af1fcf48cd5464d8ee78515bf42c7056 1768 
lirc-compat-remotes_0.9.0-1.1.debian.tar.xz
 538fd036d4e9d26bbe969efbd2b2ff6fea291d0d9deaa4a1bf1321c5b74b093c 6669 
lirc-compat-remotes_0.9.0-1.1_source.buildinfo
Files:
 b6c8143fdcecc2c9e3042439dd28eb34 1868 utils extra 

Bug#899578: marked as done (libirman: Invalid maintainer address pkg-lirc-ma...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Mon, 15 Oct 2018 16:21:36 +
with message-id 
and subject line Bug#899578: fixed in libirman 0.5.2-1.1
has caused the Debian Bug report #899578,
regarding libirman: Invalid maintainer address 
pkg-lirc-ma...@lists.alioth.debian.org
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.)


-- 
899578: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899578
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libirman
Version: 0.5.2-1
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of libirman,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package libirman since the list address
pkg-lirc-ma...@lists.alioth.debian.org used in the Maintainer: field
was not transferred to the alioth-lists service that provides a
continuation for the lists in the @lists.alioth.debian.org domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
pkg-lirc-ma...@lists.alioth.debian.org is 4.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: libirman
Source-Version: 0.5.2-1.1

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

Debian distribution maintenance software
pp.
Gianfranco Costamagna  (supplier of updated libirman 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 15 Oct 2018 18:06:39 +0200
Source: libirman
Binary: libirman-dev libirman0 lirc-drv-irman
Architecture: source
Version: 0.5.2-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Lirc Team 
Changed-By: Gianfranco Costamagna 
Description:
 libirman-dev - Library, headers and test tools for the Irman infrared hardware
 libirman0  - Shared library to access the libirman hardware
 lirc-drv-irman - LIRC plugin providing irman compatible devices support
Closes: 899578
Changes:
 libirman (0.5.2-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Update maintainer (Closes: #899578)
Checksums-Sha1:
 50d03d4031782bf903cbd4c26175967b8ba27a11 2219 libirman_0.5.2-1.1.dsc
 6c94e5ac07f95aead447f8420cb6312bc148c891 5036 libirman_0.5.2-1.1.debian.tar.xz
 c57a9770e1ea1c28599425ae8aaa3596df4654bc 6676 
libirman_0.5.2-1.1_source.buildinfo
Checksums-Sha256:
 69fe86645de220a3960855245539ab1bbb650f9fc2e159ae3fe411e916ddf53d 2219 
libirman_0.5.2-1.1.dsc
 65ce6dd002aea2b7bca8984d52090fa1f2683fe81ef14455e3a01183f1fc44fd 5036 
libirman_0.5.2-1.1.debian.tar.xz
 b3c411f42ec5c17ad56d474120076bdc6e2ee12b1e33f898a44cb3efcd57e360 6676 
libirman_0.5.2-1.1_source.buildinfo
Files:
 3651c5e85cceea354b5010754528ea45 2219 libs optional 

Bug#899663: marked as done (pylirc: Invalid maintainer address pkg-lirc-ma...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Mon, 15 Oct 2018 16:22:22 +
with message-id 
and subject line Bug#899663: fixed in pylirc 0.0.5-3.1
has caused the Debian Bug report #899663,
regarding pylirc: Invalid maintainer address 
pkg-lirc-ma...@lists.alioth.debian.org
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.)


-- 
899663: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899663
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pylirc
Version: 0.0.5-3
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of pylirc,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package pylirc since the list address
pkg-lirc-ma...@lists.alioth.debian.org used in the Maintainer: field
was not transferred to the alioth-lists service that provides a
continuation for the lists in the @lists.alioth.debian.org domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
pkg-lirc-ma...@lists.alioth.debian.org is 4.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: pylirc
Source-Version: 0.0.5-3.1

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

Debian distribution maintenance software
pp.
Gianfranco Costamagna  (supplier of updated pylirc 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 15 Oct 2018 18:10:22 +0200
Source: pylirc
Binary: python-pylirc
Architecture: source
Version: 0.0.5-3.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Lirc Team 
Changed-By: Gianfranco Costamagna 
Description:
 python-pylirc - Python bindings for Linux Infra-red Remote Control (LIRC) 
support
Closes: 899663
Changes:
 pylirc (0.0.5-3.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Update maintainer field (Closes: #899663)
Checksums-Sha1:
 4ab518ec588aa292d3182cc64c61b61f3de17696 2109 pylirc_0.0.5-3.1.dsc
 272a89cab6bb81b3f62dd866d8faadb2d05c52d9 2640 pylirc_0.0.5-3.1.debian.tar.xz
 72ad82f717ac8e79e9c9a3f36f173499f9e22c78 7262 pylirc_0.0.5-3.1_source.buildinfo
Checksums-Sha256:
 2318d3f59328007fe59a82dfa5d1644a1f4bf6cce0e56e87195258b6fabf2c9c 2109 
pylirc_0.0.5-3.1.dsc
 14f3728beefd45545f55b21b6531adb94fb338dddfe677fe07896f9a4a3e7098 2640 
pylirc_0.0.5-3.1.debian.tar.xz
 62bfa445a24db64b7b0cf7cf7e15324bee0cc679e200f94ccd9fe54e8e705fe5 7262 
pylirc_0.0.5-3.1_source.buildinfo
Files:
 f63f860200159c11358a68415cbc6189 2109 python optional pylirc_0.0.5-3.1.dsc
 5329ea1d36a89921bedaac942135bc60 2640 python optional 
pylirc_0.0.5-3.1.debian.tar.xz
 cd5355bab70a703780fe9ca72712686a 7262 python optional 

Bug#899981: marked as done (lirc: Invalid maintainer address pkg-lirc-ma...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Mon, 15 Oct 2018 16:21:43 +
with message-id 
and subject line Bug#899981: fixed in lirc 0.10.1-2
has caused the Debian Bug report #899981,
regarding lirc: Invalid maintainer address 
pkg-lirc-ma...@lists.alioth.debian.org
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.)


-- 
899981: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899981
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:lirc
Version: 0.10.0-2
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of lirc,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package lirc since the list address
pkg-lirc-ma...@lists.alioth.debian.org used in the Maintainer: field
was not transferred to the alioth-lists service that provides a
continuation for the lists in the @lists.alioth.debian.org domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
pkg-lirc-ma...@lists.alioth.debian.org is 4.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: lirc
Source-Version: 0.10.1-2

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

Debian distribution maintenance software
pp.
Gianfranco Costamagna  (supplier of updated lirc 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 15 Oct 2018 18:01:50 +0200
Source: lirc
Binary: lirc lirc-doc liblirc0 liblircclient0 liblircclient-dev liblirc-dev 
liblirc-client0 lirc-x
Architecture: source
Version: 0.10.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Lirc Team 
Changed-By: Gianfranco Costamagna 
Description:
 liblirc-client0 - infra-red remote control support - client library
 liblirc-dev - Infra-red remote control support - development files
 liblirc0   - Infra-red remote control support - Run-time libraries
 liblircclient-dev - Transitional placeholder for obsoleted liblircclient-dev
 liblircclient0 - Transitional placeholder for obsoleted liblircclient0
 lirc   - Infra-red remote control support - daemons and utils
 lirc-doc   - Infra-red remote control support - website and manual docs
 lirc-x - infra-red remote control support - X utilities
Closes: 899981
Changes:
 lirc (0.10.1-2) unstable; urgency=medium
 .
   * Team upload.
   * Update maintainer email address (Closes: #899981)
Checksums-Sha1:
 76c443b541638f9cbc26139c20559b24252da9f3 2693 lirc_0.10.1-2.dsc
 d0837ee80901d667d7400b008e992ac9aaaba676 33764 lirc_0.10.1-2.debian.tar.xz
 4533b9ac5c98fe73881e0e19504fa7252b947940 8976 lirc_0.10.1-2_source.buildinfo
Checksums-Sha256:
 

Bug#911090: libapt-pkg5.0: incompatible with apt/stretch

[Julian Andres Klode]

On Mon, Oct 15, 2018 at 05:12:10PM +0200, Andreas Beckmann wrote:
> Package: libapt-pkg5.0
> Version: 1.7.0
> Severity: serious
> 
> Hi,
> 
> I just did a partial upgrade on a stretch+buster+sid development
> system resulting in apt-get erroring out with 
> 
> apt-get: relocation error: /usr/lib/x86_64-linux-gnu/libapt-private.so.0.0: 
> symbol _ZN3URIcvNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEB5cxx11Ev 
> version APTPKG_5.0 not defined in file libapt-pkg.so.5.0 with link time 
> reference
> 
> Looks like some Breaks may be needed ...

So, I think this affects more than just apt. gcc 7 broke the ABI
by adding a new mangling

  URI::operator std::__cxx11::basic_string, 
std::allocator >()

and only linking to that. It seems that some new gcc version then
got rid of the old one

  URI::operator std::__cxx11::basic_string, 
std::allocator >[abi:cxx11]()

and now it's crashing.

And that's a problem for _every_ library with operator string(), not
just apt.

-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer  i speak de, en

Processed: pylirc: nmu ongoing

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch pending
Bug #899663 [src:pylirc] pylirc: Invalid maintainer address 
pkg-lirc-ma...@lists.alioth.debian.org
Added tag(s) pending and patch.

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

Bug#899663: pylirc: nmu ongoing

[Gianfranco Costamagna]

control: tags -1 patch pending

uploaded in unstable the following debdiff
--- pylirc-0.0.5/debian/changelog   2011-06-14 22:24:16.0 +0200
+++ pylirc-0.0.5/debian/changelog   2018-10-15 18:10:22.0 +0200
@@ -1,3 +1,10 @@
+pylirc (0.0.5-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Update maintainer field (Closes: #899663)
+
+ -- Gianfranco Costamagna   Mon, 15 Oct 2018 
18:10:22 +0200
+
 pylirc (0.0.5-3) unstable; urgency=low
 
   * Added "--with python2" to debian/rules.
diff -Nru pylirc-0.0.5/debian/control pylirc-0.0.5/debian/control
--- pylirc-0.0.5/debian/control 2011-06-14 22:20:19.0 +0200
+++ pylirc-0.0.5/debian/control 2018-10-15 18:10:16.0 +0200
@@ -1,7 +1,7 @@
 Source: pylirc
 Section: python
 Priority: optional
-Maintainer: lirc Maintainer Team 
+Maintainer: Debian Lirc Team 
 Uploaders: Loic Minier ,
Arnaud Quette ,
Charlie Smotherman ,

Bug#899578: libirman: nmu uploaded

[Gianfranco Costamagna]

Control: tags 899578 + patch
Control: tags 899578 + pending

diff -Nru libirman-0.5.2/debian/changelog libirman-0.5.2/debian/changelog
--- libirman-0.5.2/debian/changelog 2016-10-29 05:19:40.0 +0200
+++ libirman-0.5.2/debian/changelog 2018-10-15 18:06:39.0 +0200
@@ -1,3 +1,10 @@
+libirman (0.5.2-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Update maintainer (Closes: #899578)
+
+ -- Gianfranco Costamagna   Mon, 15 Oct 2018 
18:06:39 +0200
+
 libirman (0.5.2-1) unstable; urgency=medium
 
   * Team upload.
diff -Nru libirman-0.5.2/debian/control libirman-0.5.2/debian/control
--- libirman-0.5.2/debian/control   2016-10-24 22:17:48.0 +0200
+++ libirman-0.5.2/debian/control   2018-10-15 18:06:35.0 +0200
@@ -1,6 +1,6 @@
 Source: libirman
 Priority: optional
-Maintainer: lirc Maintainer Team 
+Maintainer: Debian Lirc Team 
 Uploaders: Amaya Rodrigo Sastre ,
Hector Garcia ,
Julien Danjou ,


now in unstable

G.

Processed: libirman: nmu uploaded

[Debian Bug Tracking System]

Processing control commands:

> tags 899578 + patch
Bug #899578 [src:libirman] libirman: Invalid maintainer address 
pkg-lirc-ma...@lists.alioth.debian.org
Added tag(s) patch.
> tags 899578 + pending
Bug #899578 [src:libirman] libirman: Invalid maintainer address 
pkg-lirc-ma...@lists.alioth.debian.org
Added tag(s) pending.

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

Bug#908681: libsane1: pointless package rename

[Philip Rinn]

Hi Jörg,

it seems there is an accepted solution for this bug since almost two weeks:

- rename libsane1 back to libsane
- add a "Provides: libsane1" to libsane

see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908681#51

Why isn't that route followed?

Thanks,
Philip



signature.asc
Description: OpenPGP digital signature

Bug#908681: libsane1: pointless package rename

[Philip Rinn]

On 14.10.18 at 14:35 Jeremy Bicha wrote:
> Control: severity -1 serious
> 
> On Sat, 13 Oct 2018 at 19:59:38 Philip Rinn  wrote:
>> Control: -1 severity normal
>>
>> Hi,
>>
>> I lower the severity of this bug as I couldn't find a severe violation of the
>> Debian policy - please point me to it if I missed something.
>>
>> Best,
>> Philip
> 
> This bug was filed by Julien Cristau. I believe the bug was filed in
> his role as Stable Release Manager. Therefore, serious is the
> appropriate bug severity.

True, I missed that.

Bug#911093: libjetbrains-annotations-java: missing Breaks+Replaces: libintellij-annotations-java (<< 16.0.2-4)

[Andreas Beckmann]

Package: libjetbrains-annotations-java
Version: 16.0.2-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts replaces-without-breaks

Hi,

during a test with piuparts and DOSE tools I noticed your package causes
removal of files that also belong to another package.
This is caused by using Replaces without corresponding Breaks.

The installation sequence to reproduce this problem is

  apt-get install libintellij-annotations-java/testing
  # (1)
  apt-get install libjetbrains-annotations-java/sid
  apt-get remove libjetbrains-annotations-java
  # (2)

The list of installed files at points (1) and (2) should be identical,
but the following files have disappeared:

  /usr/share/java/org.jetbrains.annotations-common-16.0.2-SNAPSHOT.jar
  /usr/share/java/org.jetbrains.annotations-common.jar
  /usr/share/java/org.jetbrains.annotations-java8-16.0.2-SNAPSHOT.jar
  /usr/share/java/org.jetbrains.annotations-java8.jar
  
/usr/share/maven-repo/org/jetbrains/annotations/16.0.2-SNAPSHOT/annotations-16.0.2-SNAPSHOT.jar
  
/usr/share/maven-repo/org/jetbrains/annotations/16.0.2-SNAPSHOT/annotations-16.0.2-SNAPSHOT.pom
  /usr/share/maven-repo/org/jetbrains/annotations/debian/annotations-debian.jar
  /usr/share/maven-repo/org/jetbrains/annotations/debian/annotations-debian.pom
  
/usr/share/maven-repo/org/jetbrains/common/16.0.2-SNAPSHOT/common-16.0.2-SNAPSHOT.jar
  
/usr/share/maven-repo/org/jetbrains/common/16.0.2-SNAPSHOT/common-16.0.2-SNAPSHOT.pom
  /usr/share/maven-repo/org/jetbrains/common/debian/common-debian.jar
  /usr/share/maven-repo/org/jetbrains/common/debian/common-debian.pom


This is a serious bug violating policy 7.6, see
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces
and also see the footnote that describes this incorrect behavior:
https://www.debian.org/doc/debian-policy/ch-relationships.html#id13

The libjetbrains-annotations-java package has the following relationships with 
libintellij-annotations-java:

  Conflicts: n/a
  Breaks:n/a
  Replaces:  libintellij-annotations-java  # unversioned

And you probably want to have

  Suggests: libjetbrains-annotations-java-doc

instead of suggesting the transitional package.
  

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

1m53.8s ERROR: FAIL: After purging files have disappeared:
  /usr/share/java/org.jetbrains.annotations-common-16.0.2-SNAPSHOT.jar   owned 
by: libjetbrains-annotations-java
  /usr/share/java/org.jetbrains.annotations-common.jar -> 
org.jetbrains.annotations-common-16.0.2-SNAPSHOT.jar   owned by: 
libjetbrains-annotations-java
  /usr/share/java/org.jetbrains.annotations-java8-16.0.2-SNAPSHOT.jarowned 
by: libjetbrains-annotations-java
  /usr/share/java/org.jetbrains.annotations-java8.jar -> 
org.jetbrains.annotations-java8-16.0.2-SNAPSHOT.jar owned by: 
libjetbrains-annotations-java
  
/usr/share/maven-repo/org/jetbrains/annotations/16.0.2-SNAPSHOT/annotations-16.0.2-SNAPSHOT.jar
 -> ../../../../../java/org.jetbrains.annotations-java8-16.0.2-SNAPSHOT.jar 
owned by: libjetbrains-annotations-java
  
/usr/share/maven-repo/org/jetbrains/annotations/16.0.2-SNAPSHOT/annotations-16.0.2-SNAPSHOT.pom
owned by: libjetbrains-annotations-java
  /usr/share/maven-repo/org/jetbrains/annotations/debian/annotations-debian.jar 
-> ../../../../../java/org.jetbrains.annotations-java8-16.0.2-SNAPSHOT.jar  
 owned by: libjetbrains-annotations-java
  /usr/share/maven-repo/org/jetbrains/annotations/debian/annotations-debian.pom 
 owned by: libjetbrains-annotations-java
  
/usr/share/maven-repo/org/jetbrains/common/16.0.2-SNAPSHOT/common-16.0.2-SNAPSHOT.jar
 -> ../../../../../java/org.jetbrains.annotations-common-16.0.2-SNAPSHOT.jar
  owned by: libjetbrains-annotations-java
  
/usr/share/maven-repo/org/jetbrains/common/16.0.2-SNAPSHOT/common-16.0.2-SNAPSHOT.pom
  owned by: libjetbrains-annotations-java
  /usr/share/maven-repo/org/jetbrains/common/debian/common-debian.jar -> 
../../../../../java/org.jetbrains.annotations-common-16.0.2-SNAPSHOT.jar
owned by: libjetbrains-annotations-java
  /usr/share/maven-repo/org/jetbrains/common/debian/common-debian.pomowned 
by: libjetbrains-annotations-java

1m53.8s ERROR: FAIL: After purging files have been modified:
  /var/lib/dpkg/info/libintellij-annotations-java.list   not owned


cheers,

Andreas


libintellij-annotations-java=16.0.2-3_libjetbrains-annotations-java=16.0.2-4.log.gz
Description: application/gzip

Bug#909099: gimagereader: crashes at startup

[Philip Rinn]

Control: block -1 by 908681

Hi,

I'm really sorry that gImageReader in testing is still not fixed. Unfortunately
it's still blocked by the back and forth due to the libsane -> libsane1 
transition
- although it's technically totally unrelated, it just happened during the same 
time.

Best,
Philip

Processed: Re: Bug#909099: gimagereader: crashes at startup

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 908681
Bug #909099 {Done: Philip Rinn } [gimagereader] 
gimagereader: crashes at startup
909099 was not blocked by any bugs.
909099 was not blocking any bugs.
Added blocking bug(s) of 909099: 908681

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

Bug#906602: marked as done (haskell-hashable: FTBFS when built with dpkg-buildpackage -A)

[Debian Bug Tracking System]

Your message dated Mon, 15 Oct 2018 15:35:18 +
with message-id 
and subject line Bug#906602: fixed in haskell-hashable 1.2.7.0-5
has caused the Debian Bug report #906602,
regarding haskell-hashable: FTBFS when built with dpkg-buildpackage -A
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.)


-- 
906602: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906602
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:haskell-hashable
Version: 1.2.7.0-2
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
test -x debian/rules
mkdir -p "."
CDBS WARNING:DEB_DH_STRIP_ARGS is deprecated since 0.4.85
CDBS WARNING:DEB_COMPRESS_EXCLUDE is deprecated since 0.4.85
. /usr/share/haskell-devscripts/Dh_Haskell.sh && \
make_setup_recipe
Running ghc --make Setup.hs -o debian/hlibrary.setup
[1 of 1] Compiling Main ( Setup.hs, Setup.o )
Linking debian/hlibrary.setup ...
. /usr/share/haskell-devscripts/Dh_Haskell.sh && \
configure_recipe
Running debian/hlibrary.setup configure --ghc -v2 
--package-db=/var/lib/ghc/package.conf.d --prefix=/usr 
--libdir=/usr/lib/haskell-packages/ghc/lib --libexecdir=/usr/lib 
--builddir=dist-ghc --ghc-option=-optl-Wl\,-z\,relro 
--haddockdir=/usr/lib/ghc-doc/haddock/hashable-1.2.7.0/ --datasubdir=hashable 
--htmldir=/usr/share/doc/libghc-hashable-doc/html/ --enable-library-profiling 
--hsc2hs-options= --gcc-options= --ghc-options=\  --enable-tests
Configuring hashable-1.2.7.0...

[... snipped ...]

Using hpc version 0.67 found on system at: /usr/bin/hpc
Using hsc2hs version 0.68.2 found on system at: /usr/bin/hsc2hs
Using hscolour version 1.24 found on system at: /usr/bin/HsColour
No jhc found
Using ld found on system at: /usr/bin/ld.gold
No lhc found
No lhc-pkg found
No pkg-config found
Using runghc version 8.2.2 found on system at: /usr/bin/runghc
Using strip version 2.31 found on system at: /usr/bin/strip
Using tar found on system at: /bin/tar
No uhc found
touch configure-ghc-stamp
. /usr/share/haskell-devscripts/Dh_Haskell.sh &&\
haddock_recipe
Running debian/hlibrary.setup haddock --builddir=dist-ghc 
--with-haddock=/usr/bin/haddock --with-ghc=ghc --verbose=2 --html --hoogle 
--haddock-options=\"--mathjax=file:///usr/share/javascript/mathjax/MathJax.js\" 
--hyperlink-source
/usr/bin/haddock --version
/usr/bin/ghc --numeric-version
/usr/bin/haddock --ghc-version 
'--mathjax=file:///usr/share/javascript/mathjax/MathJax.js'
Running hscolour for hashable-1.2.7.0...
creating dist-ghc/doc/html/hashable
creating dist-ghc/doc/html
creating dist-ghc/doc
creating dist-ghc/doc/html
creating dist-ghc/doc/html/hashable
creating dist-ghc/build
creating dist-ghc/build/autogen
creating dist-ghc/build/autogen
Preprocessing library for hashable-1.2.7.0..
creating dist-ghc/doc/html/hashable/src
/usr/bin/HsColour -print-css -odist-ghc/doc/html/hashable/src/hscolour.css
/usr/bin/HsColour -css -anchor 
-odist-ghc/doc/html/hashable/src/Data-Hashable.html Data/Hashable.hs
/usr/bin/HsColour -css -anchor 
-odist-ghc/doc/html/hashable/src/Data-Hashable-Lifted.html 
Data/Hashable/Lifted.hs
/usr/bin/HsColour -css -anchor 
-odist-ghc/doc/html/hashable/src/Data-Hashable-Class.html Data/Hashable/Class.hs
/usr/bin/HsColour -css -anchor 
-odist-ghc/doc/html/hashable/src/Data-Hashable-Generic.html 
Data/Hashable/Generic.hs
creating dist-ghc/build/tests
creating dist-ghc/build/tests/autogen
creating dist-ghc/build/tests/autogen
Preprocessing test suite 'tests' for hashable-1.2.7.0..
creating dist-ghc/build/tests/tests-tmp/Regress
creating dist-ghc/build/tests/tests-tmp
creating dist-ghc/build/tests/tests-tmp/Regress
ppHsc2hs: broken closure: []
CallStack (from HasCallStack):
  error, called at 
libraries/Cabal/Cabal/Distribution/Simple/PreProcess.hs:460:17 in 
Cabal-2.0.1.0:Distribution.Simple.PreProcessHaddock failed (no modules?), 
refusing to create empty documentation package.
make: *** [/usr/share/cdbs/1/class/hlibrary.mk:173: build-haddock-stamp] Error 1
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


To reproduce, please try "dpkg-buildpackage -A".

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.
--- End Message ---
--- Begin Message ---
Source: 

Bug#908702: linux-image-4.18.0-1-amd64 prevents use of internet (more or les

[ghpy]

Dear maintainer,

after updating from 4.18.0-1-amd64 to 4.18.0-2-amd64 the behaviour of my system 
seems to be back to normal. As far as I can see this bug is fixed for me.

Best regards and thank you for your time
G. Heine

Bug#911091: python3.5-minimal: incompatible with python3-minimal 3.5.3-1 from stretch

[Andreas Beckmann]

Package: python3.5-minimal
Version: 3.5.6-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + python3-pymca5-dbg
Control: found -1 python3-pymca5-dbg/5.4.0+dfsg-1

Hi,

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

This test intentionally skipped 'testing' to find file overwrite
problems before packages migrate from 'unstable' to 'testing'.

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

  Preparing to unpack .../02-python3.5-minimal_3.5.6-1_amd64.deb ...
  Unpacking python3.5-minimal (3.5.6-1) over (3.5.3-1) ...
  Preparing to unpack .../03-python3-numpy_1%3a1.14.5-1+b1_amd64.deb ...
  Traceback (most recent call last):
File "/usr/bin/py3clean", line 210, in 
  main()
File "/usr/bin/py3clean", line 196, in main
  pfiles = set(dpf.from_package(options.package))
File "/usr/share/python3/debpython/files.py", line 50, in from_package
  shell=True, stdout=PIPE)
File "/usr/lib/python3.5/subprocess.py", line 676, in __init__
  restore_signals, start_new_session)
File "/usr/lib/python3.5/subprocess.py", line 1221, in _execute_child
  restore_signals, start_new_session, preexec_fn)
  TypeError: fork_exec() argument 4 must be tuple, not list
  dpkg: warning: old python3-numpy package pre-removal script subprocess 
returned error exit status 1
  dpkg: trying script from the new package instead ...
  Traceback (most recent call last):
File "/usr/bin/py3clean", line 210, in 
  main()
File "/usr/bin/py3clean", line 196, in main
  pfiles = set(dpf.from_package(options.package))
File "/usr/share/python3/debpython/files.py", line 50, in from_package
  shell=True, stdout=PIPE)
File "/usr/lib/python3.5/subprocess.py", line 676, in __init__
  restore_signals, start_new_session)
File "/usr/lib/python3.5/subprocess.py", line 1221, in _execute_child
  restore_signals, start_new_session, preexec_fn)
  TypeError: fork_exec() argument 4 must be tuple, not list
  dpkg: error processing archive 
/tmp/apt-dpkg-install-sEY2kl/03-python3-numpy_1%3a1.14.5-1+b1_amd64.deb 
(--unpack):
   new python3-numpy package pre-removal script subprocess returned error exit 
status 1
  Traceback (most recent call last):
File "/usr/bin/py3compile", line 290, in 
  main()
File "/usr/bin/py3compile", line 270, in main
  options.force, options.optimize, e_patterns)
File "/usr/bin/py3compile", line 147, in compile
  next(coroutine)
File "/usr/bin/py3compile", line 133, in py_compile
  stdin=PIPE, close_fds=True)
File "/usr/lib/python3.5/subprocess.py", line 676, in __init__
  restore_signals, start_new_session)
File "/usr/lib/python3.5/subprocess.py", line 1221, in _execute_child
  restore_signals, start_new_session, preexec_fn)
  TypeError: fork_exec() argument 4 must be tuple, not list
  dpkg: error while cleaning up:
   installed python3-numpy package post-installation script subprocess returned 
error exit status 1

At this point python3-minimal 3.5.3-1 is still installed.


I hope I traced this bug to the correct package, and as such that
it will disappear once python3.5 gets removed from unstable.
It's curious that this only happened for a single package.


cheers,

Andreas


python3-pymca5-dbg_5.4.0+dfsg-1.log.gz
Description: application/gzip

Processed: python3.5-minimal: incompatible with python3-minimal 3.5.3-1 from stretch

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + python3-pymca5-dbg
Bug #911091 [python3.5-minimal] python3.5-minimal: incompatible with 
python3-minimal 3.5.3-1 from stretch
Added indication that 911091 affects python3-pymca5-dbg
> found -1 python3-pymca5-dbg/5.4.0+dfsg-1
Bug #911091 [python3.5-minimal] python3.5-minimal: incompatible with 
python3-minimal 3.5.3-1 from stretch
The source python3-pymca5-dbg and version 5.4.0+dfsg-1 do not appear to match 
any binary packages
Marked as found in versions python3-pymca5-dbg/5.4.0+dfsg-1.

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

Bug#910861: Update

[Bruninksbeek]

Dear maintainer


I wrote that I use Debian Jessie with the MATE desktop environment. 
However, I should have written that I use Stretch with the MATE desktop 
environment. I upgraded from Jessie to Stretch only two months ago.


Furthermore, the Bug Tracking System has indicated that 
mate-system-tools 1.8.1+dfsg1-2 belongs to Oldstable, which struck me in 
particular.


I submitted my bug report to mate-system-tools, not knowing that that 
package does not belong to Stretch.


It has turned out that I still had 35 packages that belonged to Jessie 
installed, and I also had 145 remnant configurations of packages that 
belonged to Jessie.


I have removed the 35 obsolete packages and the 145 remnant 
configurations.


However, the problem remains.

The application to manage the main menu of MATE shows that the command 
line that is used for 'Users and groups' is 'mate-users-admin'. That 
command is obsolete in Stretch, but I do not know what it should be.


Furthermore, it still is not possible to start the application to manage 
users and groups from the MATE Configuration Centre.


So there seem to be serious configuration faults in MATE resulting from 
upgrading from Jessie to Stretch.



Kind regards

Maarten

Bug#911090: libapt-pkg5.0: incompatible with apt/stretch

[Andreas Beckmann]

Package: libapt-pkg5.0
Version: 1.7.0
Severity: serious

Hi,

I just did a partial upgrade on a stretch+buster+sid development
system resulting in apt-get erroring out with 

apt-get: relocation error: /usr/lib/x86_64-linux-gnu/libapt-private.so.0.0: 
symbol _ZN3URIcvNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEB5cxx11Ev 
version APTPKG_5.0 not defined in file libapt-pkg.so.5.0 with link time 
reference

Looks like some Breaks may be needed ...

probably the relevant package mixture:

ii  apt 1.4.8amd64commandline package manager
ii  dpkg1.19.2   amd64Debian package management 
system
ii  libapt-pkg5.0:amd64 1.7.0amd64package management runtime 
library


Andreas

Processed: Re: Bug#886394: pdfsam still shows the same error although it does give the banner as gimp does while starting up.

[Debian Bug Tracking System]

Processing control commands:

> severity -1 grave
Bug #886394 [pdfsam] java.lang.ClassNotFoundException: javafx.scene.layout.HBox
Severity set to 'grave' from 'important'
> block -1 by 910764
Bug #886394 [pdfsam] java.lang.ClassNotFoundException: javafx.scene.layout.HBox
886394 was not blocked by any bugs.
886394 was not blocking any bugs.
Added blocking bug(s) of 886394: 910764

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

Bug#911073: gtimelog fails to start with ValueError (`Namespace Soup not available`)

[Marius Gedminas]

On Mon, Oct 15, 2018 at 12:55:54PM +0200, Michael Schubert wrote:
> ./gtimelog currently fails with the following traceback:
> 
> Traceback (most recent call last):
>   File "/usr/bin/gtimelog", line 11, in 
...
>   File "/usr/lib/python3/dist-packages/gtimelog/main.py", line 55, in 
> gi.require_version('Soup', '2.4')
>   File "/usr/lib/python3/dist-packages/gi/__init__.py", line 127, in 
> require_version
> raise ValueError('Namespace %s not available' % namespace)
> ValueError: Namespace Soup not available

Looks like a missing Depends: on gir1.2-soup-2.4

> Versions of packages gtimelog depends on:
> ii  dconf-gsettings-backend [gsettings-backend]  0.30.0-1
> ii  gir1.2-appindicator3-0.1 0.4.92-7
> ii  gir1.2-gtk-3.0   3.24.1-2
> ii  gir1.2-pango-1.0 1.42.4-3
> ii  python3  3.6.6-1
> ii  python3-gi   3.30.1-1
> ii  python3-setuptools   40.2.0-1
> 
> gtimelog recommends no packages.
> 
> Versions of packages gtimelog suggests:
> ii  mutt   1.10.1-2
> pn  vim-gnome  

Oh, also gtimelog 0.11 no longer uses an external email client so the
Suggests: on mutt should be dropped.

Regards,
Marius Gedminas
-- 
Fibers (sic, geddit?) are a Windows lightweight alternative to threads, which
combine the pleasure of the Win32 threading interface with the intellectual
opportunity afforded by the coroutine.
-- Verity Stob

Bug#868411: gniall: Port to GTK+ 3

[Jeremy Bicha]

On Mon, Oct 15, 2018 at 9:13 AM Yavor Doganov  wrote:
> Jeremy Bicha wrote:
> > On Sun, Oct 14, 2018 at 5:00 PM Yavor Doganov  wrote:
> > > I am not in a position to decide the faith of a package that I do not
> > > maintain.
> >
> > With its very low popcon and the fact that it has no maintainer in
> > Debian (or anywhere), I think your opinion is the most important here.
> >
> > If you want it to stay in Debian, I can sponsor your upload.
> > Otherwise, I can file the removal bug now.
>
> Please do what you think is best.  I am just an occasional contributor
> providing a patch; I cannot decide whether this package should be
> removed.

No. I'm delegating this decision to you. There is no upstream. There
is no Debian maintainer. You're the closest we have to either one of
those for this package.

By creating these patches, you are making a statement that you believe
these apps are worth saving. Otherwise, I or someone else would
eventually file removal bugs for all these packages.

Thanks,
Jeremy Bicha

Bug#911084: sagemath crashes as cantor backend

[Kinky Nekoboi]

Package: sagemath
Version: 8.3-3
Severity: serious
Justification: unkown

as above
cantor-sage-backend crashes with Segmentation fault.



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

Kernel: Linux 4.18.0-2-amd64 (SMP w/2 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 sagemath depends on:
ii  cysignals-tools  1.6.7+ds-4
ii  cython   0.28.4-1
ii  ecl  16.1.2-4+b1
ii  eclib-tools  20171002-1+b3
ii  f2c  20160102-1
ii  fflas-ffpack 2.3.2-3
ii  flintqs  1:1.0-3
ii  gap-core 4r8p8-3
ii  gfan 0.6.2-2
ii  gmp-ecm  7.0.4+ds-3
ii  ipython  5.5.0-1
ii  iso-codes4.1-1
ii  jmol 14.6.4+2016.11.05+dfsg1-3.1
ii  lcalc1.23+dfsg-7
ii  less 487-0.1+b1
ii  libatlas3-base [liblapack.so.3]  3.10.3-7+b1
ii  libblas3 [libblas.so.3]  3.8.0-1+b1
ii  libbrial-groebner3   1.2.0-2
ii  libbrial31.2.0-2
ii  libc62.27-6
ii  libcdd-tools 094h-1+b1
ii  libcliquer1  1.21-2
ii  libec3   20171002-1+b3
ii  libecm1  7.0.4+ds-3
ii  libflint-2.5.2   2.5.2-18
ii  libflint-arb21:2.14.0-4
ii  libgap-sage-44.8.8+3+20160327g69a66f0+dsx-1
ii  libgcc1  1:8.2.0-7
ii  libgd3   2.2.5-4
ii  libgivaro9   4.0.4-2
ii  libglpk404.65-2
ii  libgmp10 2:6.1.2+dfsg-3
ii  libgmpxx4ldbl2:6.1.2+dfsg-3
ii  libgsl23 2.5+dfsg-5
ii  libgslcblas0 2.5+dfsg-5
ii  libiml0  1.0.4-1+b2
ii  libjs-mathjax2.7.4+dfsg-1
ii  libjs-three  80+dfsg2-2
ii  liblapack3 [liblapack.so.3]  3.8.0-1+b1
ii  liblfunction01.23+dfsg-7
ii  liblinbox-1.5.2-01.5.2-2
ii  liblinboxsage-1.5.2-01.5.2-2
ii  liblrcalc1   1.2-2+b1
ii  libm4ri-0.0.20140914 20140914-2+b1
ii  libm4rie-0.0.2015090820150908-2
ii  libmpc3  1.1.0-1
ii  libmpfi0 1.5.3+ds-2
ii  libmpfr6 4.0.1-1
ii  libntl35 10.5.0-2
ii  libopenblas-base [liblapack.so.3]0.3.3+ds-1
ii  libpari-gmp-tls6 2.11.0-1
ii  libplanarity03.0.0.5-3
ii  libpng16-16  1.6.34-2
ii  libppl14 1:1.2-3
ii  libpynac18   0.7.22-3
ii  libratpoints-2.1.3   1:2.1.3-1+b2
ii  libreadline7 7.0-5
ii  librw0   0.8+ds-1
ii  libsingular4 1:4.1.1-p2+ds-2
ii  libstdc++6   8.2.0-7
ii  libsymmetrica2   2.0+ds-5
ii  libzn-poly-0.9   0.9-3+b2
ii  maxima-sage  5.41.0+ds-2
ii  maxima-sage-doc  5.41.0+ds-2
ii  maxima-sage-share5.41.0+ds-2
ii  nauty2.6r10+ds-1
ii  octave   4.4.1-2
ii  palp 2.1-5
ii  pari-doc 2.11.0-1
ii  pari-galdata 0.20080411-2
ii  pari-gp  2.11.0-1
ii  pari-seadata 0.20090618-1
ii  python   2.7.15-3
ii  python-alabaster 0.7.8-1
ii  python-babel   

Bug#909837: bug 909837 is forwarded to https://github.com/libreswan/libreswan/issues/206, closing 909837

[Daniel Kahn Gillmor]

forwarded 909837 https://github.com/libreswan/libreswan/issues/206
close 909837 3.27-1
thanks

Processed: bug 909837 is forwarded to https://github.com/libreswan/libreswan/issues/206, closing 909837

[Debian Bug Tracking System]

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

> forwarded 909837 https://github.com/libreswan/libreswan/issues/206
Bug #909837 [src:libreswan] libreswan: FTBFS on armel, armhf, i386, mips, mipsel
Bug #909839 [src:libreswan] libreswan FTBFS on 32bit
Set Bug forwarded-to-address to 
'https://github.com/libreswan/libreswan/issues/206'.
Set Bug forwarded-to-address to 
'https://github.com/libreswan/libreswan/issues/206'.
> close 909837 3.27-1
Bug #909837 [src:libreswan] libreswan: FTBFS on armel, armhf, i386, mips, mipsel
Bug #909839 [src:libreswan] libreswan FTBFS on 32bit
Marked as fixed in versions libreswan/3.27-1.
Marked as fixed in versions libreswan/3.27-1.
Bug #909837 [src:libreswan] libreswan: FTBFS on armel, armhf, i386, mips, mipsel
Bug #909839 [src:libreswan] libreswan FTBFS on 32bit
Marked Bug as done
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#910964: libprotobuf17 might need Breaks: libprotobuf10

[Adrian Bunk]

On Mon, Oct 15, 2018 at 06:33:50PM +0530, Pirate Praveen wrote:
> On Sat, 13 Oct 2018 23:42:59 +0300 Adrian Bunk  wrote:
> > Package: libprotobuf17
> > Version: 3.6.1-2
> > Severity: serious
> > Control: affects -1 src:cura-engine
>
> I think this was caused by another dependency still built against older
> protobuf.
>...

Yes, that's what I also suspect.

When it has been observed that ending up with both libprotobuf10 and 
libprotobuf17 in a binary will not work, then this should be expressed 
through the package dependencies.

That would avoid a couple of potential problems in situations like 
stretch->buster upgrades or for testing users.

It should also fix the autopkgtest failures that are currently
preventing protobuf from entering testing this month.

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Bug#910974: Bug #910974 in utidylib marked as pending

[Michal Čihař]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/modules/utidylib/commit/ee107c6a6d907348cb7b37e1f5ae0859f9ebbcf8


New upstream release.

* New upstream release.
  - Fixes operation with recent html-tidy (Closes: #910974).
  - Adds support for Python 3.



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/910974

Processed: Bug #910974 in utidylib marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #910974 [src:utidylib] utidylib: FTBFS with new tidy-html5 5.7.16: 
Build-dep list needs updating, test fails (upstream behaviour change)
Added tag(s) pending.

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

Bug#911067: chromium: Conflict with chrome-gnome-shell /etc/chromium

[Patrick Franz]

Hi

On Mon, 15 Oct 2018 12:28:05 +0200  wrote:
> Package: chromium
> Version: 70.0.3538.54-1
> Severity: serious
> Justification: Policy 10.7.4
> 
> dpkg: erreur de traitement de l'archive /var/cache/apt/archives/
chromium_70.0.3538.54-2_amd64.deb (--unpack) :
>  tentative de remplacement du répertoire « /etc/chromium » dans le 
paquet chrome-gnome-shell 10.1-1 avec un élément de type différent

In my case, it conflicts with plasma-browser-integration, but I think 
it's the same error:

dpkg: Fehler beim Bearbeiten des Archivs /var/cache/apt/archives/
chromium_70.0.3538.54-2_amd64.deb (--unpack):
 Versuch, Verzeichnis »/etc/chromium« in Paket plasma-browser-
integration 5.13.5-1 mit Nichtverzeichnis zu überschreiben


Essentially it says, that it tries to override /etc/chromium in the 
package plasma-browser-integration with a "non-directory".


-- 
Med vänliga hälsningar

Patrick Franz

Bug#868411: gniall: Port to GTK+ 3

[Yavor Doganov]

Jeremy Bicha wrote:
> On Sun, Oct 14, 2018 at 5:00 PM Yavor Doganov  wrote:
> > I am not in a position to decide the faith of a package that I do not
> > maintain.
> 
> With its very low popcon and the fact that it has no maintainer in
> Debian (or anywhere), I think your opinion is the most important here.
> 
> If you want it to stay in Debian, I can sponsor your upload.
> Otherwise, I can file the removal bug now.

Please do what you think is best.  I am just an occasional contributor
providing a patch; I cannot decide whether this package should be
removed.

> I think this is the oldest app I've seen in Debian (based on its
> last upstream release and maintainer upload and lack of NMUs).

The lack of NMUs is a clear indication that it doesn't require
frequent changes and therefore is not a maintenance burden.

Bug#840377: marked as done (pyepl: Please remove build dependency on jade)

[Debian Bug Tracking System]

Your message dated Mon, 15 Oct 2018 13:06:29 +
with message-id 
and subject line Bug#840377: fixed in pyepl 1.1.0+git12-g365f8e3-3
has caused the Debian Bug report #840377,
regarding pyepl: Please remove build dependency on jade
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.)


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

The pyepl has a build dependency on jade which is obsolete and will be
removed from Debian.  It doesn't appears that pyepl needs jade at all,
so it can simply be removed.

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

Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-- 
Neil Roeth
--- End Message ---
--- Begin Message ---
Source: pyepl
Source-Version: 1.1.0+git12-g365f8e3-3

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated pyepl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 15 Oct 2018 14:05:00 +0200
Source: pyepl
Binary: python-pyepl python-pyepl-common
Architecture: source
Version: 1.1.0+git12-g365f8e3-3
Distribution: unstable
Urgency: medium
Maintainer: NeuroDebian Team 
Changed-By: Andreas Tille 
Description:
 python-pyepl - module for coding psychology experiments in Python
 python-pyepl-common - module for coding psychology experiments in Python
Closes: 840377 866459
Changes:
 pyepl (1.1.0+git12-g365f8e3-3) unstable; urgency=medium
 .
   * Team upload.
   * debian/gbp.conf: Set packaging branch name debian
   * Drop Build-Depends: jade
 Closes: #840377
   * Depends: s/python-imaging/python-pil/
 Closes: #866459
   * Build-Depends: dh-python
   * DEP5 fixes
   * debhelper 10
   * Point Vcs fields to salsa.debian.org
   * Standards-Version: 4.2.1
   * Testsuite: autopkgtest-pkg-python
   * Drop ancient field X-Python-Version
   * Remove obsolete debian/pycompat
   * DEP3 fields
   * d/rules: Short dh
   * Add some Depends to Build-Depends to run unit tests
   * hardening=+all
Checksums-Sha1:
 99175b6a33a8ddde9441dc1acc1a79d44f220266 2333 pyepl_1.1.0+git12-g365f8e3-3.dsc
 7204eca86c91265214f95d762adefd22238033e5 7320 
pyepl_1.1.0+git12-g365f8e3-3.debian.tar.xz
Checksums-Sha256:
 b0ad1d256d71e330f2c38a631ed9a354f6e566d070f441328fe3e4dcabcfce79 2333 
pyepl_1.1.0+git12-g365f8e3-3.dsc
 d8bdbaa819005c15f8945e42343f93cd893887707d6de9b489cc6dec6ef556a4 7320 
pyepl_1.1.0+git12-g365f8e3-3.debian.tar.xz
Files:
 01a81bac4ae47cb6c686e71ae4545b74 2333 python optional 
pyepl_1.1.0+git12-g365f8e3-3.dsc
 910132c2c7130fdee3da2368ee79c314 7320 python optional 
pyepl_1.1.0+git12-g365f8e3-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlvEhfIRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtFX3BAAiKCl+8RbnrlcVCOJlV9ekG7UmHgsWHV6
voR126CxDnp3ikLO9F06yLxOxSKbMbnPk/VEa4WQZRNAhwaV9DRD/46I4zBCycTN
UWjSdjizlW7MMI1RcbePmO/RJOxxoys9eFAjnX2FSIT1RYPFBFzokjRKL2hopa0y
M8jbGR45bktvN7lhFlY3vMStZuS+D7/yXjvIFsr0naCIdCO7aDHSqelLv+7Fy7zL
zUA2dttXssaCmiqCiuUTryo8gX8cE/91kKLAz2PIOhreIrY/Yb8zgqVMTgBZzGTS
AexFbbDXQsKfsnkjNYW7Mg4cIoQ5nZuciWyO6cEX3JqBCD9ruHUQva21Uys0cmXn
7yzbFJaADnv3XxD/QGDEfgWfexEhy+WW4mOC/P+elYVVLQf78ByqA1A+8bVDSx/l
NUFxb/Wqx+qWb2MAE/lizYfHE+LDNvmkO3jEVSx9iz0DeAYlDmPu6fkcR46mbLW7
qEc/EjtIGO9OOw4uOgV4PJASZuUcVxkHCPxetVK/irqb75bMEFKjCih0TG5ZyIyP
ZoJBXARozLM3V2QMyQ4jQj1VFaow6dbDtEC+8oHK9TZNTlOGtaIYnIN+4fSnQt85
Ulq1uoNJ9F/N48AmAnrSkTHNtk5g/vcoOiVbWLiu/HN8iY5sXAESbDWWGc1jJjqt
8LwBq2lHTn4=
=8Lfb
-END PGP SIGNATURE End Message ---

Bug#911068: marked as done (ranger: broken symlinks: /etc/ranger/*/*.* -> /usr/lib/python3.6/dist-packages/ranger/*/*.*)

[Debian Bug Tracking System]

Your message dated Mon, 15 Oct 2018 13:07:21 +
with message-id 
and subject line Bug#911068: fixed in ranger 1.9.2-2
has caused the Debian Bug report #911068,
regarding ranger: broken symlinks: /etc/ranger/*/*.* -> 
/usr/lib/python3.6/dist-packages/ranger/*/*.*
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.)


-- 
911068: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911068
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ranger
Version: 1.9.2-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...):

  /etc/ranger/data/scope.sh -> 
/usr/lib/python3.6/dist-packages/ranger/data/scope.sh (ranger)
  /etc/ranger/data/mime.types -> 
/usr/lib/python3.6/dist-packages/ranger/data/mime.types (ranger)
  /etc/ranger/config/rifle.conf -> 
/usr/lib/python3.6/dist-packages/ranger/config/rifle.conf (ranger)
  /etc/ranger/config/rc.conf -> 
/usr/lib/python3.6/dist-packages/ranger/config/rc.conf (ranger)
  /etc/ranger/config/commands.py -> 
/usr/lib/python3.6/dist-packages/ranger/config/commands.py (ranger)

All the targeted files seem to be shipped as 
  /usr/lib/python3/dist-packages/ranger/*/*.*
instead.

Assuming the package does not work properly without its bits in /etc,
I set the severity to serious.


cheers,

Andreas


ranger_1.9.2-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: ranger
Source-Version: 1.9.2-2

We believe that the bug you reported is fixed in the latest version of
ranger, 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.
Mo Zhou  (supplier of updated ranger package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 15 Oct 2018 12:06:12 +
Source: ranger
Binary: ranger
Architecture: source
Version: 1.9.2-2
Distribution: unstable
Urgency: medium
Maintainer: Vern Sun 
Changed-By: Mo Zhou 
Description:
 ranger - File manager with an ncurses frontend written in Python
Closes: 911068
Changes:
 ranger (1.9.2-2) unstable; urgency=medium
 .
   * Fix broken symlinks: /etc/ranger/.* -> /usr/lib/python3.6/.*
 It should point to /usr/lib/python3/.* instead. (Closes: #911068)
Checksums-Sha1:
 cdf82b786b6298d8904f1c243c3aa8f20f95c72f  ranger_1.9.2-2.dsc
 1d9253fd6d703bea926aad5ba8cbe5d53672ff35 11128 ranger_1.9.2-2.debian.tar.xz
 dbd08a7ecf4870490255ffdfbc33a4d8b457410e 6884 ranger_1.9.2-2_source.buildinfo
Checksums-Sha256:
 c1d965fcc57d82b713218fa2a2a8808631d78e17368236620b06f016a5965b5d  
ranger_1.9.2-2.dsc
 cc9dc5c32232de049fc2c151f31a987850709e1f0883728674f7f1770a357a7e 11128 
ranger_1.9.2-2.debian.tar.xz
 7b75f9995149f303ed13dfff5b3d00566fd2aab025770eb041d76e2378b154fc 6884 
ranger_1.9.2-2_source.buildinfo
Files:
 dc862d435b7c46ce42dd891ec851ecf1  utils optional ranger_1.9.2-2.dsc
 2813fe6d0c3df905217702e0940b0113 11128 utils optional 
ranger_1.9.2-2.debian.tar.xz
 4b4744f4c6f81a9b2897bcee599a785c 6884 utils optional 
ranger_1.9.2-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEY4vHXsHlxYkGfjXeYmRes19oaooFAlvEhJQACgkQYmRes19o
aop4PA//ebjpaGmHZWjUrG3hL/FupklpXa9HQHydxKDIrtyR3DGswzgzfD1F+/nW
gaanICQbZzaIuGQG/Uv9/3jMcI42xWjkv/APQxEDf3jp92E/fKq9UKiUJxkJuLEB
wmLXYH/5wtjPMXVN/TDgAJn9cSjngortDgpffxVik8H5XPlfwehKngzCOSV+iTbf
w0ffibYC4DcSQzx0nH2qFEH48STN8jv9GjgeYzwjG+lvnucUOIy9gcTrolxHsqxj
a47ax2kujIVeqmqkm8XzQqX58mHZabw+WTYj9kgvsEL5nMNPVcpzzrkmY5nPduFi
j3uIaPVM0pywVGyuDUNBxxqAbFcUqn9bm940pJ6GAb0RJm7NRc9NEc1jwW2dgtpe
UrgxFgL7joTPnWQmW/DHcFZJHxul8b7Y+AdSmsbuCzuSXymQwz7r8tbEL/jzpdOP
HV2toyuRWRiyxmHHUj+CnyD+kq4U++Gs68yQKri78Oeh4qoc9Rc9N1w/atUv3i8Y
KliJpNJxK3cbbyl/I7JQQctJPCorHGvwiZRRIXvQrMRFbIOhEb7/Pw6W1vCDGCFE
GMYRHxbhACUVlmDcrYUkvPbVtiihxH6ibijJGHVIZDaaLzWUlN1vbuN59G6SgYoo
4iAhLspKf3oT8P5SLP3uqRvRis5tNoabesvswkCC5QJPrK0bbHo=
=nBnV
-END PGP SIGNATURE End Message ---

Bug#866459: marked as done (pyepl: depends on obsolete python-imaging (replace with python3-pil or python-pil))

[Debian Bug Tracking System]

Your message dated Mon, 15 Oct 2018 13:06:29 +
with message-id 
and subject line Bug#866459: fixed in pyepl 1.1.0+git12-g365f8e3-3
has caused the Debian Bug report #866459,
regarding pyepl: depends on obsolete python-imaging (replace with python3-pil 
or python-pil)
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.)


-- 
866459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866459
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pyepl
Version: 1.1.0+git12-g365f8e3-2
Severity: important
Tags: sid buster
User: d...@debian.org
Usertags: imaging-pillow

One or more binary packages built from this source depends on or
recommends python-imaging, which is obsolete for some years now.
Please build the source using the python-pil package. If your
package doesn't need to be built with Python2, please consider using
Python3 and depend on python3-pil.

Planning to remove python-imaging for the buster release, so the
severity of this issues might be raised.
--- End Message ---
--- Begin Message ---
Source: pyepl
Source-Version: 1.1.0+git12-g365f8e3-3

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated pyepl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 15 Oct 2018 14:05:00 +0200
Source: pyepl
Binary: python-pyepl python-pyepl-common
Architecture: source
Version: 1.1.0+git12-g365f8e3-3
Distribution: unstable
Urgency: medium
Maintainer: NeuroDebian Team 
Changed-By: Andreas Tille 
Description:
 python-pyepl - module for coding psychology experiments in Python
 python-pyepl-common - module for coding psychology experiments in Python
Closes: 840377 866459
Changes:
 pyepl (1.1.0+git12-g365f8e3-3) unstable; urgency=medium
 .
   * Team upload.
   * debian/gbp.conf: Set packaging branch name debian
   * Drop Build-Depends: jade
 Closes: #840377
   * Depends: s/python-imaging/python-pil/
 Closes: #866459
   * Build-Depends: dh-python
   * DEP5 fixes
   * debhelper 10
   * Point Vcs fields to salsa.debian.org
   * Standards-Version: 4.2.1
   * Testsuite: autopkgtest-pkg-python
   * Drop ancient field X-Python-Version
   * Remove obsolete debian/pycompat
   * DEP3 fields
   * d/rules: Short dh
   * Add some Depends to Build-Depends to run unit tests
   * hardening=+all
Checksums-Sha1:
 99175b6a33a8ddde9441dc1acc1a79d44f220266 2333 pyepl_1.1.0+git12-g365f8e3-3.dsc
 7204eca86c91265214f95d762adefd22238033e5 7320 
pyepl_1.1.0+git12-g365f8e3-3.debian.tar.xz
Checksums-Sha256:
 b0ad1d256d71e330f2c38a631ed9a354f6e566d070f441328fe3e4dcabcfce79 2333 
pyepl_1.1.0+git12-g365f8e3-3.dsc
 d8bdbaa819005c15f8945e42343f93cd893887707d6de9b489cc6dec6ef556a4 7320 
pyepl_1.1.0+git12-g365f8e3-3.debian.tar.xz
Files:
 01a81bac4ae47cb6c686e71ae4545b74 2333 python optional 
pyepl_1.1.0+git12-g365f8e3-3.dsc
 910132c2c7130fdee3da2368ee79c314 7320 python optional 
pyepl_1.1.0+git12-g365f8e3-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlvEhfIRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtFX3BAAiKCl+8RbnrlcVCOJlV9ekG7UmHgsWHV6
voR126CxDnp3ikLO9F06yLxOxSKbMbnPk/VEa4WQZRNAhwaV9DRD/46I4zBCycTN
UWjSdjizlW7MMI1RcbePmO/RJOxxoys9eFAjnX2FSIT1RYPFBFzokjRKL2hopa0y
M8jbGR45bktvN7lhFlY3vMStZuS+D7/yXjvIFsr0naCIdCO7aDHSqelLv+7Fy7zL
zUA2dttXssaCmiqCiuUTryo8gX8cE/91kKLAz2PIOhreIrY/Yb8zgqVMTgBZzGTS
AexFbbDXQsKfsnkjNYW7Mg4cIoQ5nZuciWyO6cEX3JqBCD9ruHUQva21Uys0cmXn
7yzbFJaADnv3XxD/QGDEfgWfexEhy+WW4mOC/P+elYVVLQf78ByqA1A+8bVDSx/l
NUFxb/Wqx+qWb2MAE/lizYfHE+LDNvmkO3jEVSx9iz0DeAYlDmPu6fkcR46mbLW7
qEc/EjtIGO9OOw4uOgV4PJASZuUcVxkHCPxetVK/irqb75bMEFKjCih0TG5ZyIyP
ZoJBXARozLM3V2QMyQ4jQj1VFaow6dbDtEC+8oHK9TZNTlOGtaIYnIN+4fSnQt85
Ulq1uoNJ9F/N48AmAnrSkTHNtk5g/vcoOiVbWLiu/HN8iY5sXAESbDWWGc1jJjqt
8LwBq2lHTn4=
=8Lfb
-END PGP SIGNATURE End Message ---

Processed: notfound 910806 in 4.9.0.2652-3

[Debian Bug Tracking System]

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

> notfound 910806 4.9.0.2652-3
Bug #910806 {Done: Alexandre Rossi } [davmail] 
Latest testing update (4.9.0.2652-2) fails to execute in daemon mode
Ignoring request to alter found versions of bug #910806 to the same values 
previously set
> thanks
Stopping processing here.

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

Processed: Re: Bug#911079: [pdfsam] Window blank

[Debian Bug Tracking System]

Processing control commands:

> tags -1 unreproducible
Bug #911079 [pdfsam] [pdfsam] Window blank
Added tag(s) unreproducible.
> severity -1 important
Bug #911079 [pdfsam] [pdfsam] Window blank
Severity set to 'important' from 'grave'

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

Bug#911079: [pdfsam] Window blank

[Markus Koschany]

Control: tags -1 unreproducible
Control: severity -1 important

Am 15.10.18 um 14:11 schrieb Marco Righi:
> Package: pdfsam
> Version: 1.1.4-4
> Severity: grave
> 
> --- Please enter the report below this line. ---
> Hi,
> After pdfsam execution appears only a little box (see image_1).
> After enlarging the little box, the window is blank (see image_2).
> Thx
> --- System information. ---
> Architecture: Kernel:   Linux 4.9.0-8-amd64
> 
> Debian Release: 9.5
>   500 xenial  updates.signal.org   500 xenial
> ppa.launchpad.net   500 stable-updates  ftp.it.debian.org   500 stable
> security.debian.org   500 stable  repo.skype.com   500
> stable  packages.microsoft.com   500 stable
> ftp.it.debian.org   500 stable  dl.google.com   500 stable
> deb.debian.org   500 cosmic  ppa.launchpad.net
> --- Package information. ---

Hi,

I can't reproduce this issue on Debian Stretch with Gnome 3. Everything
works as intended. Your apt-cache policy looks rather unusual. Perhaps a
package from a different repository than debian.org causes this error.

Regards,

Markus



signature.asc
Description: OpenPGP digital signature

Bug#900998: marked as done (gambas3: FTBFS w/SDL2 2.0.7+: MIX_INIT_FLUIDSYNTH undeclared)

[Debian Bug Tracking System]

Your message dated Mon, 15 Oct 2018 13:59:24 +0200
with message-id <027cd8ae-21bd-fb02-db36-7e7730a9e...@fishpost.de>
and subject line gambas3: FTBFS w/SDL2 2.0.7+: MIX_INIT_FLUIDSYNTH undeclared
has caused the Debian Bug report #900998,
regarding gambas3: FTBFS w/SDL2 2.0.7+: MIX_INIT_FLUIDSYNTH undeclared
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.)


-- 
900998: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900998
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gambas3
Version: 3.9.2-2
Severity: serious
Tags: upstream
Justification: fails to build from source (but built successfully in the past)

Builds (binNMUs, for the most part) of gambas3 have been failing for
months:

CC   gb_sdl2_audio_la-main.lo
  main.c: In function 'AUDIO_init':
  main.c:61:13: error: 'MIX_INIT_FLUIDSYNTH' undeclared (first use in this 
function); did you mean 'MIX_INIT_MID'?
init_mixer(MIX_INIT_FLUIDSYNTH, "FLUIDSYNTH");
   ^~~
   MIX_INIT_MID
  main.c:61:13: note: each undeclared identifier is reported only once for each 
function it appears in
  Makefile:512: recipe for target 'gb_sdl2_audio_la-main.lo' failed

This problem first showed up on buildd.debian.org with December's
binNMU for libpoppler72 (subsequently superseded by libpoppler73 and
libpoppler74), and has continued to affect subsequent binNMU attempts,
first for libncurses6 and most recently for libcurl4.  This latest
round of failures is particularly problematic because it interferes
with a *hard* transition, in which libcurl4 conflicts with libcurl3 to
avoid skew in some scenarios (as detailed in #858398).

Could you please take a look?

Thanks!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
--- End Message ---
--- Begin Message ---
Package: gambas3
Version: 3.11.4-1

This bug is closed upstream. The fix is available in the Debian package
version 3.11.4-1.--- End Message ---

Bug#911078: triplea: Fails to start with NullPointerException

[Markus Koschany]

Package: triplea
Version: 1.9.0.0.7062-2
Severity: grave
Justification: renders package unusable

After the switch to OpenJFX 11, triplea fails to start with a
NullPointerException.

triplea.engine.version.bin:1.9
java.lang.NullPointerException
at 
org.pushingpixels.substance.internal.utils.SubstanceColorUtilities.getDefaultBackgroundColor(SubstanceColorUtilities.java:759)
at 
org.pushingpixels.substance.internal.utils.SubstanceColorUtilities.getBackgroundFillColor(SubstanceColorUtilities.java:661)
at 
org.pushingpixels.substance.internal.ui.SubstancePanelUI.__org__pushingpixels__substance__internal__ui__SubstancePanelUI__installDefaults(SubstancePanelUI.java:74)
at 
org.pushingpixels.substance.internal.ui.SubstancePanelUI.installDefaults(SubstancePanelUI.java)
at 
java.desktop/javax.swing.plaf.basic.BasicPanelUI.installUI(BasicPanelUI.java:62)
at 
org.pushingpixels.substance.internal.ui.SubstancePanelUI.__org__pushingpixels__substance__internal__ui__SubstancePanelUI__installUI(SubstancePanelUI.java)
at 
org.pushingpixels.substance.internal.ui.SubstancePanelUI.installUI(SubstancePanelUI.java)
at java.desktop/javax.swing.JComponent.setUI(JComponent.java:685)
at java.desktop/javax.swing.JPanel.setUI(JPanel.java:150)
at java.desktop/javax.swing.JPanel.updateUI(JPanel.java:126)
at java.desktop/javax.swing.JPanel.(JPanel.java:86)
at java.desktop/javax.swing.JPanel.(JPanel.java:109)
at java.desktop/javax.swing.JPanel.(JPanel.java:117)
at 
games.strategy.engine.framework.startup.ui.SetupPanel.(SetupPanel.java:25)
at 
games.strategy.engine.framework.startup.ui.MetaSetupPanel.(MetaSetupPanel.java:45)
at 
games.strategy.engine.framework.startup.mc.SetupPanelModel.showSelectType(SetupPanelModel.java:33)
at 
games.strategy.engine.framework.GameRunner.lambda$main$0(GameRunner.java:159)
at 
java.desktop/java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:313)
at 
java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:770)
at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:721)
at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:715)
at java.base/java.security.AccessController.doPrivileged(Native Method)
at 
java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85)
at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:740)
at 
java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203)
at 
java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124)
at 
java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:113)
at 
java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:109)
at 
java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
at 
java.desktop/java.awt.EventDispatchThread.run(EventDispatchThread.java:90)
java.lang.NullPointerException
at 
games.strategy.engine.framework.GameRunner.lambda$showMainFrame$4(GameRunner.java:255)
at 
java.desktop/java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:313)
at 
java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:770)
at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:721)
at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:715)
at java.base/java.security.AccessController.doPrivileged(Native Method)
at 
java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85)
at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:740)
at 
games.strategy.engine.framework.GameRunner$1.dispatchEvent(GameRunner.java:330)
at 
java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203)
at 
java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124)
at 
java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:113)
at 
java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:109)
at 
java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
at 
java.desktop/java.awt.EventDispatchThread.run(EventDispatchThread.java:90)
java.lang.NullPointerException
at 
games.strategy.engine.framework.GameRunner.lambda$showMainFrame$4(GameRunner.java:255)
at 
java.desktop/java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:313)
at 
java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:770)
at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:721)
at 

Processed: user debian...@lists.debian.org, usertagging 910836, severity of 911049 is serious, affects 910150

[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 910836 piuparts
There were no usertags set.
Usertags are now: piuparts.
> severity 911049 serious
Bug #911049 [libcmark-gfm-dev,libcmark-gfm-extensions-dev] 
libcmark-gfm{,-extensions}-dev: missing Depends: libcmark-gfm{,-extensions}0 (= 
${binary:Version})
Severity set to 'serious' from 'normal'
> affects 910150 + obs-utils
Bug #910150 [obs-build] obs-build: broken symlinks: 
/usr/lib/obs-build/configs/{stretch,buster}.conf -> unstable.conf
Added indication that 910150 affects obs-utils
> thanks
Stopping processing here.

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

Bug#911073: gtimelog fails to start with ValueError (`Namespace Soup not available`)

[Michael Schubert]

Package: gtimelog
Version: 0.11.1-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

./gtimelog currently fails with the following traceback:

Traceback (most recent call last):
  File "/usr/bin/gtimelog", line 11, in 
load_entry_point('gtimelog==0.11.1', 'gui_scripts', 'gtimelog')()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 484, in 
load_entry_point
return get_distribution(dist).load_entry_point(group, name)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2707, 
in load_entry_point
return ep.load()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2325, 
in load
return self.resolve()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2331, 
in resolve
module = __import__(self.module_name, fromlist=['__name__'], level=0)
  File "/usr/lib/python3/dist-packages/gtimelog/main.py", line 55, in 
gi.require_version('Soup', '2.4')
  File "/usr/lib/python3/dist-packages/gi/__init__.py", line 127, in 
require_version
raise ValueError('Namespace %s not available' % namespace)
ValueError: Namespace Soup not available


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

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

Versions of packages gtimelog depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.30.0-1
ii  gir1.2-appindicator3-0.1 0.4.92-7
ii  gir1.2-gtk-3.0   3.24.1-2
ii  gir1.2-pango-1.0 1.42.4-3
ii  python3  3.6.6-1
ii  python3-gi   3.30.1-1
ii  python3-setuptools   40.2.0-1

gtimelog recommends no packages.

Versions of packages gtimelog suggests:
ii  mutt   1.10.1-2
pn  vim-gnome  

-- no debconf information

Bug#908947: youtube-dl: backport youtube-dl to recent version for stretch

[Holger Levsen]

On Sun, Oct 14, 2018 at 04:02:06PM -0300, Rogério Brito wrote:
> Second, I would like to more formally update youtube-dl for stable releases 
> in conjunction with Holger.

yay!

> So, what is the way to proceed with updates to stable releases? I've never 
> done that before.

you file a bug against release.debian.org using the 'stretch-pu'
category and then attach the debdiff between the current version in
stable and the version you want to upgrade too.

best you use reportbug for this, as it will help to get the meta-data
right.

also if the debdiff is too big (40k iirc), the mail/bug will not be send
to the release list. in this case better include the "debdiff|diffstat"
output when filing the bug and then reply to the bug-confirmation mail
with the actuall full diff.


-- 
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#911068: ranger: broken symlinks: /etc/ranger/*/*.* -> /usr/lib/python3.6/dist-packages/ranger/*/*.*

[Andreas Beckmann]

Package: ranger
Version: 1.9.2-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...):

  /etc/ranger/data/scope.sh -> 
/usr/lib/python3.6/dist-packages/ranger/data/scope.sh (ranger)
  /etc/ranger/data/mime.types -> 
/usr/lib/python3.6/dist-packages/ranger/data/mime.types (ranger)
  /etc/ranger/config/rifle.conf -> 
/usr/lib/python3.6/dist-packages/ranger/config/rifle.conf (ranger)
  /etc/ranger/config/rc.conf -> 
/usr/lib/python3.6/dist-packages/ranger/config/rc.conf (ranger)
  /etc/ranger/config/commands.py -> 
/usr/lib/python3.6/dist-packages/ranger/config/commands.py (ranger)

All the targeted files seem to be shipped as 
  /usr/lib/python3/dist-packages/ranger/*/*.*
instead.

Assuming the package does not work properly without its bits in /etc,
I set the severity to serious.


cheers,

Andreas


ranger_1.9.2-1.log.gz
Description: application/gzip

Bug#897806: lmms: ftbfs with GCC-8

[Holger Levsen]

On Sun, Oct 14, 2018 at 03:08:34AM +0200, Javier Serrano Polo wrote:
> El ds 13 de 10 de 2018 a les 11:14 +, Holger Levsen va escriure:
> > why don't you attach your fix to this bug?
> Because I am the lazy maintainer.

shrugs then.


-- 
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#911067: chromium: Conflict with chrome-gnome-shell /etc/chromium

[Jérémy Lal]

Package: chromium
Version: 70.0.3538.54-1
Severity: serious
Justification: Policy 10.7.4

dpkg: erreur de traitement de l'archive 
/var/cache/apt/archives/chromium_70.0.3538.54-2_amd64.deb (--unpack) :
 tentative de remplacement du répertoire « /etc/chromium » dans le paquet 
chrome-gnome-shell 10.1-1 avec un élément de type différent

Regards,
Jérémy

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

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

Versions of packages chromium depends on:
ii  chromium-common  70.0.3538.54-2
ii  libasound2   1.1.6-1
ii  libatk-bridge2.0-0   2.30.0-2
ii  libatk1.0-0  2.30.0-1
ii  libatomic1   8.2.0-7
ii  libavcodec58 7:4.0.2-2+b2
ii  libavformat587:4.0.2-2+b2
ii  libavutil56  7:4.0.2-2+b2
ii  libc62.27-6
ii  libcairo-gobject21.15.12-1
ii  libcairo21.15.12-1
ii  libcups2 2.2.8-5
ii  libdbus-1-3  1.12.10-1
ii  libdrm2  2.4.95-1
ii  libevent-2.1-6   2.1.8-stable-4
ii  libexpat12.2.6-1
ii  libflac8 1.3.2-3
ii  libfontconfig1   2.13.1-1
ii  libfreetype6 2.8.1-2
ii  libgcc1  1:8.2.0-7
ii  libgdk-pixbuf2.0-0   2.38.0+dfsg-6
ii  libglib2.0-0 2.58.1-2
ii  libgtk-3-0   3.24.1-2
ii  libharfbuzz0b1.9.0-1
ii  libicu60 60.2-6
ii  libjpeg62-turbo  1:1.5.2-2+b1
ii  liblcms2-2   2.9-3
ii  libminizip1  1.1-8+b1
ii  libnspr4 2:4.20-1
ii  libnss3  2:3.39-1
ii  libopenjp2-7 2.3.0-1
ii  libopus0 1.3~beta+20180518-1
ii  libpango-1.0-0   1.42.4-3
ii  libpangocairo-1.0-0  1.42.4-3
ii  libpci3  1:3.5.2-1
ii  libpng16-16  1.6.34-2
ii  libpulse012.2-2
ii  libre2-4 20180901+dfsg-1
ii  libsnappy1v5 1.1.7-1
ii  libstdc++6   8.2.0-7
ii  libvpx5  1.7.0-3
ii  libwebp6 0.6.1-2
ii  libwebpdemux20.6.1-2
ii  libwebpmux3  0.6.1-2
ii  libx11-6 2:1.6.7-1
ii  libx11-xcb1  2:1.6.7-1
ii  libxcb1  1.13.1-1
ii  libxcomposite1   1:0.4.4-2
ii  libxcursor1  1:1.1.15-1
ii  libxdamage1  1:1.1.4-3
ii  libxext6 2:1.3.3-1+b2
ii  libxfixes3   1:5.0.3-1
ii  libxi6   2:1.7.9-1
ii  libxml2  2.9.4+dfsg1-7+b1
ii  libxrandr2   2:1.5.1-1
ii  libxrender1  1:0.9.10-1
ii  libxslt1.1   1.1.32-2
ii  libxss1  1:1.2.3-1
ii  libxtst6 2:1.2.3-1
ii  zlib1g   1:1.2.11.dfsg-1

chromium recommends no packages.

Versions of packages chromium suggests:
pn  chromium-driver  
iu  chromium-l10n70.0.3538.54-2
pn  chromium-shell   

-- no debconf information

Bug#894359: Now we have antlr 4.6 - any chance to get 4.7 soon (Was: beast-mcmc2: Cannot find symbol CharStreams.fromString(newick))

[Andrius Merkys]

Hi Andreas,

On 10/15/2018 12:54 PM, Andreas Tille wrote:
> when I tried last time we had antlr 4.5.  I now tried with 4.6 but it
> seems 4.7 is really needed.  Any chance to get this soon?

I am interested in packaging antlr 4.7 (with Cpp support, needed for #902798), 
I am working on it right now.

Best,
Andrius

-- 
Andrius Merkys
Vilnius University Institute of Biotechnology, Saulėtekio al. 7, room V325
LT-10257 Vilnius, Lithuania

Bug#910446: NMU diff (substantive patches in git-format-patch form)

[Ian Jackson]

Guido Günther writes ("Re: Bug#910446: NMU diff (substantive patches in 
git-format-patch form)"):
> It's not that much trouble for me but rather sad that people spent time
> on (in this case) just tedious work while they could fix other stuff
> in the same time since the maintainer is already on it.

Ah.  Well, then, thanks for your consideration.

I hope you are able to use most of what I did.  I expect if you rebase
my series onto your master with a conflict strategy of just taking
master's version, you'll have most of it done.

As an aside, I looked for a way to *extend* rather than *specify* the
flake8 ignore list.  I found that it is possible to fish the existing
list out of the relevant python module, but I didn't know how to write
such a programmatic thing in setup.cfg.

Regards,
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#894359: Now we have antlr 4.6 - any chance to get 4.7 soon (Was: beast-mcmc2: Cannot find symbol CharStreams.fromString(newick))

[Andreas Tille]

Hi,

when I tried last time we had antlr 4.5.  I now tried with 4.6 but it
seems 4.7 is really needed.  Any chance to get this soon?

Kind regards

Andreas.

On Sat, Aug 04, 2018 at 11:23:42AM +0200, Andreas Tille wrote:
> On Thu, Jul 19, 2018 at 09:44:30AM +0200, Emmanuel Bourg wrote:
> > Hi Andreas,
> > 
> > Le 19/07/2018 à 08:56, Andreas Tille a écrit :
> > 
> > > [javac] 
> > > /build/beast2-mcmc-2.5.0+dfsg/src/beast/util/TreeParser.java:353: error: 
> > > cannot find symbol
> > > [javac] CharStream charStream = 
> > > CharStreams.fromString(newick);
> > > [javac] ^
> > > [javac]   symbol:   variable CharStreams
> > > [javac]   location: class TreeParser
> > > [javac] 
> > > /build/beast2-mcmc-2.5.0+dfsg/src/beast/util/treeparser/NewickLexer.java:98:
> > >  error: method does not override or implement a method from a supertype
> > > [javac] @Override
> > > [javac] ^
> > 
> > It looks like these errors are related to ANTLR [1].
> > You'll need the version 4.7.
> 
> Upstream confirmed this[2] - and suggests to use antlr 4.7.
> So my question is: Can we expect this version of antlr in Debian
> in the foreseeable future?
> 
> Kind regards
> 
>  Andreas.
>  
> > [1] https://github.com/CompEvol/beast2/commit/deacdc96
> [2] https://github.com/CompEvol/beast2/issues/797
> 
> -- 
> http://fam-tille.de

-- 
http://fam-tille.de

Bug#907952: marked as done (openvswitch-common: Fails to install due to file conflict)

[Debian Bug Tracking System]

Your message dated Mon, 15 Oct 2018 08:38:05 +
with message-id 
and subject line Bug#907952: fixed in openvswitch 
2.10.0+2018.08.28+git.8ca7c82b7d+ds1-6
has caused the Debian Bug report #907952,
regarding openvswitch-common: Fails to install due to file conflict
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.)


-- 
907952: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907952
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openvswitch-common
Version: 2.10.0+2018.08.28+git.8ca7c82b7d+ds1-1
Severity: serious
Justification: Fails to install or upgrade

My upgrade on unstable failed today:

Preparing to unpack 
.../openvswitch-common_2.10.0+2018.08.28+git.8ca7c82b7d+ds1-1_amd64.deb ...
Unpacking openvswitch-common (2.10.0+2018.08.28+git.8ca7c82b7d+ds1-1) over 
(2.8.1+dfsg1-7) ...
dpkg: error processing archive 
/var/cache/apt/archives/openvswitch-common_2.10.0+2018.08.28+git.8ca7c82b7d+ds1-1_amd64.deb
 (--unpack):
 trying to overwrite '/usr/share/openvswitch/scripts/ovs-check-dead-ifs', which 
is also in package openvswitch-switch 2.10.0+2018.08.28+git.8ca7c82b7d+ds1-1
Errors were encountered while processing:
 
/var/cache/apt/archives/openvswitch-common_2.10.0+2018.08.28+git.8ca7c82b7d+ds1-1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

Downgrading to 2.8.1+dfsg1-7 solves the problem.
$ sudo apt install openvswitch-common=2.8.1+dfsg1-7 
openvswitch-switch=2.8.1+dfsg1-7

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

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

Versions of packages openvswitch-common depends on:
ii  libatomic1  8.2.0-4
ii  libc6   2.27-5
ii  libssl1.1   1.1.1~~pre9-1
ii  openssl 1.1.1~~pre9-1
ii  python  2.7.15-3
ii  python-six  1.11.0-2

openvswitch-common recommends no packages.

Versions of packages openvswitch-common suggests:
pn  ethtool  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: openvswitch
Source-Version: 2.10.0+2018.08.28+git.8ca7c82b7d+ds1-6

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated openvswitch package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 15 Oct 2018 09:31:42 +0200
Source: openvswitch
Binary: openvswitch-common openvswitch-dbg openvswitch-dev openvswitch-pki 
openvswitch-switch openvswitch-testcontroller openvswitch-vtep ovn-central 
ovn-controller-vtep ovn-host python-openvswitch python3-openvswitch
Architecture: source amd64 all
Version: 2.10.0+2018.08.28+git.8ca7c82b7d+ds1-6
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Thomas Goirand 
Description:
 openvswitch-common - Open vSwitch common components
 openvswitch-dbg - Debug symbols for Open vSwitch packages
 openvswitch-dev - Open vSwitch development package
 openvswitch-pki - Open vSwitch public key infrastructure dependency package
 openvswitch-switch - Open vSwitch switch implementations
 openvswitch-testcontroller - Simple controller for testing OpenFlow setups
 openvswitch-vtep - Open vSwitch VTEP utilities
 ovn-central - OVN central components
 ovn-controller-vtep - OVN vtep controller
 ovn-host   - OVN host components
 python-openvswitch - Python bindings for Open vSwitch
 python3-openvswitch - Python 3 bindings for Open vSwitch
Closes: 907952
Changes:
 openvswitch (2.10.0+2018.08.28+git.8ca7c82b7d+ds1-6) unstable; urgency=medium
 .
   * Fixed files present in 2 binaries (Closes: #907952).
Checksums-Sha1:
 e8efe9d34ec4eb7eca356eb11ae8210416249e04 3320 
openvswitch_2.10.0+2018.08.28+git.8ca7c82b7d+ds1-6.dsc
 

Bug#911061: ukui-control-center depends on nonexisting package gnome-control-center-faces

[Adrian Bunk]

Package: ukui-control-center
Version: 1.1.6-1
Severity: serious

The following packages have unmet dependencies:
 ukui-control-center : Depends: gnome-control-center-faces but it is not 
installable

Bug#911056: chromium,webext-browserpass: impossible to install chromium and webext-browserpass together

[Sven Joachim]

On 2018-10-15 10:12 +0200, Jonas Smedegaard wrote:

> Package: chromium,webext-browserpass
> Severity: serious
> Justification: 7
>
> With chromium 70.0.3538.54-1 and webext-browserpass 2.0.11+dfsg-2 installed,
> attempting to upgrade to chromium 70.0.3538.54-2 fails:
>
> Gør klar til at udpakke .../chromium_70.0.3538.54-2_amd64.deb ...
> Udpakker chromium (70.0.3538.54-2) over (70.0.3538.54-1) ...
> dpkg: advarsel: chromium: konfigurationsfil '/etc/chromium' er hverken en 
> almindelig fil eller symbolsk lænke (= '/etc/chromium')
> dpkg: fejl under behandling af arkivet 
> /var/cache/apt/archives/chromium_70.0.3538.54-2_amd64.deb (--unpack):
>  forsøger at overskrive kataloget '/etc/chromium' i pakken webext-browserpass 
> 2.0.11+dfsg-2 med ikke-katalog
> dpkg-deb: fejl: indsæt subprocess was killed by signal (Kanalen blev brudt)
> dpkg: overvejer at afkonfigurere chromium, som ville være i konflikt med 
> installation af chromium-common ...
> dpkg: ja, vil afkonfigurere chromium (ødelagt af chromium-common)
> Gør klar til at udpakke .../chromium-common_70.0.3538.54-2_amd64.deb ...
> Afkonfigurerer chromium (70.0.3538.54-1) ...
> Udpakker chromium-common (70.0.3538.54-2) over (70.0.3538.54-1) ...
> Der opstod fejl under behandlingen:
>  /var/cache/apt/archives/chromium_70.0.3538.54-2_amd64.deb
> needrestart is being skipped since dpkg has failed
> E: Sub-process /usr/bin/dpkg returned an error code (1)
> Sætter chromium-common (70.0.3538.54-2) op ...
> dpkg: afhængighedsproblemer forhindrer konfiguration af chromium:
>  chromium afhænger af chromium-common (= 70.0.3538.54-1); men:
>   Version af chromium-common på systemet er 70.0.3538.54-2.
>  chromium-common (70.0.3538.54-2) ødelægger chromium (<< 70.0.3538.54-2) og 
> er installeret.
>   Versionen af chromium, der skal sætte op, er 70.0.3538.54-1.
>
> Above is in danish, but I guess the essence is noticable for english speakers:
> /etc/chromium is somehow "owned" by both packages,
> which causes trouble (now that chromium adds a conffile, I guess).

Actually the problem is that chromium 70.0.3538.54-2 introduces
/etc/chromium as a conffile while webext-browserpass (and other
packages) ship it as a directory.

,
| $ apt-file search etc/chromium/
| chrome-gnome-shell: 
/etc/chromium/native-messaging-hosts/org.gnome.chrome_gnome_shell.json
| debian-edu-config: /etc/chromium/policies/managed/chromium-networked-prefs
| plasma-browser-integration: 
/etc/chromium/native-messaging-hosts/org.kde.plasma.browser_integration.json
| webext-browserpass: 
/etc/chromium/native-messaging-hosts/com.dannyvankooten.browserpass.json
`

Cheers,
   Sven

Bug#909035: marked as done (dependency missing to libx11-protocol-perl)

[Debian Bug Tracking System]

Your message dated Mon, 15 Oct 2018 10:28:55 +0200
with message-id <20181015082855.qr3ufszgbqhmx...@sk2.org>
and subject line Re: Bug#909035: dependency missing to libx11-protocol-perl
has caused the Debian Bug report #909035,
regarding dependency missing to libx11-protocol-perl
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.)


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

Package: retroarch
Version: 1.7.3+dfsg1-1

When start retroarch it shows the following error output:

$ retroarch
Can't locate X11/Protocol.pm in @INC (you may need to install the X11::Protocol 
module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.26.2 
/usr/local/share/perl/5.26.2 /usr/lib/x86_64-linux-gnu/perl5/5.26 
/usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.26 /usr/share/perl/5.26 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at -e line 6.
BEGIN failed--compilation aborted at -e line 6.

After installing "libx11-protocol-perl" and restarting retroarch the error 
output is gone.

Thanks,
Patrick
--- End Message ---
--- Begin Message ---
On Mon, Sep 17, 2018 at 08:28:06PM +0200, Patrick Ammann wrote:
> When start retroarch it shows the following error output:
> 
> $ retroarch
> Can't locate X11/Protocol.pm in @INC (you may need to install the 
> X11::Protocol module) (@INC contains: /etc/perl 
> /usr/local/lib/x86_64-linux-gnu/perl/5.26.2 /usr/local/share/perl/5.26.2 
> /usr/lib/x86_64-linux-gnu/perl5/5.26 /usr/share/perl5 
> /usr/lib/x86_64-linux-gnu/perl/5.26 /usr/share/perl/5.26 
> /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at -e line 6.
> BEGIN failed--compilation aborted at -e line 6.
> 
> After installing "libx11-protocol-perl" and restarting retroarch the error 
> output is gone.

This message is caused by xdg-screensaver, which is part of xdg-utils,
which recommends libx11-protocol-perl. The latter is only needed for
GNOME, which is why it’s only a recommendation.

Regards,

Stephen


signature.asc
Description: PGP signature
--- End Message ---

Bug#911025: Transition to postgresql-11

[Christoph Berg]

Re: Jeremy Bicha 2018-10-15 

> How soon do you need this issue fixed? I'm ok with glom being removed
> from Testing if that helps.

At the moment the biggest blocker is that llvm-toolchain-7 is not in
testing (OOM when stripping on mips(el)), so it's not urgent anyway.
But that could change anytime.

Can I help with the transition?

Christoph

Bug#911056: chromium,webext-browserpass: impossible to install chromium and webext-browserpass together

[Jonas Smedegaard]

Package: chromium,webext-browserpass
Severity: serious
Justification: 7

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

With chromium 70.0.3538.54-1 and webext-browserpass 2.0.11+dfsg-2 installed,
attempting to upgrade to chromium 70.0.3538.54-2 fails:

Gør klar til at udpakke .../chromium_70.0.3538.54-2_amd64.deb ...
Udpakker chromium (70.0.3538.54-2) over (70.0.3538.54-1) ...
dpkg: advarsel: chromium: konfigurationsfil '/etc/chromium' er hverken en 
almindelig fil eller symbolsk lænke (= '/etc/chromium')
dpkg: fejl under behandling af arkivet 
/var/cache/apt/archives/chromium_70.0.3538.54-2_amd64.deb (--unpack):
 forsøger at overskrive kataloget '/etc/chromium' i pakken webext-browserpass 
2.0.11+dfsg-2 med ikke-katalog
dpkg-deb: fejl: indsæt subprocess was killed by signal (Kanalen blev brudt)
dpkg: overvejer at afkonfigurere chromium, som ville være i konflikt med 
installation af chromium-common ...
dpkg: ja, vil afkonfigurere chromium (ødelagt af chromium-common)
Gør klar til at udpakke .../chromium-common_70.0.3538.54-2_amd64.deb ...
Afkonfigurerer chromium (70.0.3538.54-1) ...
Udpakker chromium-common (70.0.3538.54-2) over (70.0.3538.54-1) ...
Der opstod fejl under behandlingen:
 /var/cache/apt/archives/chromium_70.0.3538.54-2_amd64.deb
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)
Sætter chromium-common (70.0.3538.54-2) op ...
dpkg: afhængighedsproblemer forhindrer konfiguration af chromium:
 chromium afhænger af chromium-common (= 70.0.3538.54-1); men:
  Version af chromium-common på systemet er 70.0.3538.54-2.
 chromium-common (70.0.3538.54-2) ødelægger chromium (<< 70.0.3538.54-2) og er 
installeret.
  Versionen af chromium, der skal sætte op, er 70.0.3538.54-1.

Above is in danish, but I guess the essence is noticable for english speakers:
/etc/chromium is somehow "owned" by both packages,
which causes trouble (now that chromium adds a conffile, I guess).


 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAlvES+gACgkQLHwxRsGg
ASFPSg//dJyfUQDj6noxTQtxCNNR8dCW1YOw4OTRUUnGRsxfMdxnbV5+XRCJMmxI
VExT3IHQq+FZ2AVP5DYisI/w1cfhQJjSYuuCikURkgZMruony/Rz96vTNP/sHx0E
iswlJcWElPGokMNLk6DQr5Jkwn1bMVM1V0WDdW4P+8PkTPfQx3q4s9c9nvw8mbgn
Er4y+yIHxQdT+rpz6eP4sb2aymsKV2dnLqzBzIRVQBGkuuEtPhCixCqe4lm7bcYL
1uvDDMkCIfOiYK4UR8mqya/ns1A5z8EtPTT7b2wE8WaI9RuHBGxnktpBO4bBNgN9
PaZ0qtt2jVwgXgNTmZp2SpDCTvDzhfw2SiOMp2OV8MGI5di9cV9VDSSmpj7PxVlR
Qh+PL8Wj/vBSbwBULe40xXqXVGo2DznLXMA5WCH1CH3BScW4QloxcU2jhKMemK2f
K/hPpvPa9dMBLKvcpHyud15feckqWmFIahlkc1xbYxmYwDP//whoKnn5YiOMoeKk
I/czfAQ6+xSQV4W0kFf0TzA814ME1w7J6xmGtee/qFQ6/TuORWmxivDtmXqvaaLi
nxAbeLiNE9Rv/hDWg/oL7TEymYEEleLz3raLPfArA/kFFT7pKAMZjhi7gj7KMrOh
YavYvJk/j+uhfSWFBgEiQXTMQRJYijZDq8HxasFVuvC8EK6/k5c=
=MA/A
-END PGP SIGNATURE-

Bug#910446: NMU diff (substantive patches in git-format-patch form)

[Guido Günther]

Hi,
On Sun, Oct 14, 2018 at 10:55:10PM +0100, Ian Jackson wrote:
> Guido Günther writes ("Re: Bug#910446: NMU diff (substantive patches in 
> git-format-patch form)"):
> > On Sun, Oct 14, 2018 at 03:36:49PM +0100, Ian Jackson wrote:
> > > Hi.  I fixed this bug, and some other FTBFS, and am about to upload
> > > the result.  I'm doing this myself, right away, because this is an RC
> > > bug which has triggered the autoremover to want to remove dgit.
> > > 
> > > Following the recommendation in dev ref 5.11.1, I have not use
> > > DELAYED; and because I doubt that actually uploading it now will cause
> > > you any difficulty.  I hope that's OK.
> > > 
> > > The patches I made are attached.  You can also find this as a git
> > > branch, here:
> ...> 
> > That's actually not what I prefer since I
> 
> Sorry about that.  But,
>
> I did look in the bug [1] before starting work, this lunchtime UK
> time, and there was no response there.
> 
> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910446
> 
> I have just checked the bug again, and your message to it crossed with
> my decision to go ahead with the upload.  The timestamp on the
> relevant .changes file shows that I did my formal build-for-upload at
> 14:28 UTC.  I and evidently spent a few minutes getting my NMU diff
> email into shape and I sent that email at 14:36 and did the actual
> dgit push at 14:37.
> 
> Your message to the bug was at 14:31 UTC.  I confess didn't check the
> bug again in the 9 minutes between `dgit sbuild' and `dgit push'.
> 
> To be honest, if you had said any time in the past week, in the bug,
> that you were intending to fix it I would have been quite happy to
> leave the work to you.  But there was nothing from you in the bug and
> the upstream git server (which I was able to see via http, even if the
> git interface was giving me trouble) showed no recent activiy.

To be honest I saw that bug but forgot about it until I saw the
autoremoval mail. I then notified the BTS so reverse dependencies don't
need to worry.

> > - there's plenty of time until the autoremoval hits us
> 
> I'm generally quite busy and I had time and headspace to do this
> technical work now.  I wasn't confident that that would occur again in
> the next few weeks.
> 
> I'm sorry to be told that I have engaged in "sub par interaction".  I
> was trying to help.  Can you explain to me what concrete problem my
> action has caused you ?

It's not that much trouble for me but rather sad that people spent time
on (in this case) just tedious work while they could fix other stuff
in the same time since the maintainer is already on it.

> I appreciate that being the recipient, several times a year, of
> autoremoval notifications (not just from gbp) is a hazard of sitting
> on top of a large dependency stack.  But it would be nice to be able
> to at least fix these things oneself without being criticised.
> 
> It would be really helpful if people would respond to RC bugs *before*
> their entire reverse dependency stack has received an `autoremoval'
> email.

Yept, that's totally true but I think the reverse holds as well: if
things are flagged check with the maintainer(s) how this happened
(in this case it was just an oversight). They might either be working on
a fix or might be happy about an NMU.

> I guess I can be criticised for not emailing the bug before starting
> work.  Looking at my irc transcript it looks like I started at 12:00
> UTC or so.  Of course once one has started on something like this it
> is very discouraging to be told to stop and throw one's work away -
> and I guess your message to the bug was prompted by the autoremoval
> mail which had been sent ovrnight, so an additional mail from me would
> have waited anyway.  So probably in this case if I had emailed the bug
> at 12:00ish UTC it would have made no difference.

That's why I at least check with maintainers before starting work on
things. Even then it doesn't always help to avoid duplicated work (since
some times there's more than two parties involved) but most of the time
it does.

I should have used better words in my previous mail. Sorry if this came
over rougher than it meat to be.

Cheers,
 -- Guido

Bug#891096: planet-venus: python-beautifulsoup is replaced with python-bs4

[Jonas Smedegaard]

Quoting Paul Wise (2018-10-15 05:49:46)
> On Tue, 02 Oct 2018 00:57:59 +0200 Jonas Smedegaard wrote:
> 
> > planet-venus only reference BeautifulSoup in a vendor dir which is fully 
> > patched out and therefore irrelevant.
> 
> In that case the Recommends should be removed, reopening.

Oh, indeed. Silly me!

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

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


signature.asc
Description: signature

Processed: Re: Bug#909110: serious

[Debian Bug Tracking System]

Processing control commands:

> notfixed -1 7.3.0~rc2-2
Bug #909110 {Done: Ondřej Surý } [php7.3-dev] Extraneous 'L' 
in /usr/bin/phpize7.3
No longer marked as fixed in versions 7.3.0~rc2-2.
> fixed -1 7.3.0~rc3-1
Bug #909110 {Done: Ondřej Surý } [php7.3-dev] Extraneous 'L' 
in /usr/bin/phpize7.3
There is no source info for the package 'php7.3-dev' at version '7.3.0~rc3-1' 
with architecture ''
Unable to make a source version for version '7.3.0~rc3-1'
Marked as fixed in versions 7.3.0~rc3-1.

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

Bug#909110: serious

[Ondřej Surý]

Control: notfixed -1 7.3.0~rc2-2
Control: fixed -1 7.3.0~rc3-1

No, I am sorry, you are right, it was correctly fixed in 7.3.0~rc2-3, and it’s 
also included in 7.3.0~rc3-1 that I just uploaded.

Ondrej
--
Ondřej Surý
ond...@sury.org



> On 15 Oct 2018, at 08:55, Kunal Mehta  wrote:
> 
> Hi,
> 
> On 10/14/18 11:45 PM, Ondřej Surý wrote:
>> Version: 7.3.0~rc2-2
>> 
>> This had been already fixed in version in both unstable and testing.
> 
> That's not what I see...
> 
> $ php -v
> PHP 7.3.0RC2 (cli) (built: Oct 14 2018 10:21:01) ( NTS )
> Copyright (c) 1997-2018 The PHP Group
> Zend Engine v3.3.0-dev, Copyright (c) 1998-2018 Zend Technologies
>with Zend OPcache v7.3.0RC2, Copyright (c) 1999-2018, by Zend
> Technologies
> $ dpkg -l | grep php7.3-dev
> ii  php7.3-dev 7.3.0~rc2-2+b1
> amd64Files for PHP7.3 module development
> 
> $ phpize7.3
> Configuring for:
> PHP Api Version: 20180731
> Zend Module Api No:  20180731
> Zend Extension Api No:   320180731
> cp: cannot stat 'run-tests*.phpL': No such file or directory
> 
> Looking at the file directly, I can see the L:
> $ grep "\"L" /usr/bin/phpize7.3
> FILES="acinclude.m4 Makefile.global config.sub config.guess ltmain.sh
> run-tests*.php"L
> 
> 
> Am I missing something?
> 
> -- Kunal
>