Bug#674107: Processed: Re: Bug#674107: mx: Consider dropping libcluttergesture-dev build-depends

[PaulLiu]

Hi Jeremy,

Sounds ok. But abandoned upstream doesn't mean this lib is useless. To me I
think it just works. The gadgets provides by this lib is just doing what it
is without needed to upgrade or update.
I'd like to remove it for a while because I didn't work for moblin anymore.
But considering the popcon it shows there are sill some people who are
installing it and not installing bisho. That makes a question that is there
a Debian derivation that is still using mx somewhere that I'm not aware of?
And I always hope that they can upload their derivations back to Debian
when time goes by.

I'll let this question open for a month. If no any Debian derivations (or
people) propose to keep mx in main then I'll start RoM.

Yours,
Paul


On Tue, Dec 26, 2017 at 8:45 AM, Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:

> Processing control commands:
>
> > severity -1 serious
> Bug #674107 [mx] mx: Consider dropping libcluttergesture-dev build-depends
> Severity set to 'serious' from 'wishlist'
>
> --
> 674107: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674107
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>

Bug#885321: dolibarr: CVE-2017-17897 CVE-2017-17898 CVE-2017-17899 CVE-2017-17900

[Salvatore Bonaccorso]

Source: dolibarr
Version: 3.5.5+dfsg1-1
Severity: grave
Tags: patch security upstream

Hi,

the following vulnerabilities were published for dolibarr.

CVE-2017-17897[0]:
| SQL injection vulnerability in comm/multiprix.php in Dolibarr ERP/CRM
| version 6.0.4 allows remote attackers to execute arbitrary SQL commands
| via the id parameter.

CVE-2017-17898[1]:
| Dolibarr ERP/CRM version 6.0.4 does not block direct requests to
| *.tpl.php files, which allows remote attackers to obtain sensitive
| information.

CVE-2017-17899[2]:
| SQL injection vulnerability in adherents/subscription/info.php in
| Dolibarr ERP/CRM version 6.0.4 allows remote attackers to execute
| arbitrary SQL commands via the rowid parameter.

CVE-2017-17900[3]:
| SQL injection vulnerability in fourn/index.php in Dolibarr ERP/CRM
| version 6.0.4 allows remote attackers to execute arbitrary SQL commands
| via the socid parameter.

If you fix the vulnerabilities please also make sure to include the
CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-17897
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-17897
[1] https://security-tracker.debian.org/tracker/CVE-2017-17898
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-17898
[2] https://security-tracker.debian.org/tracker/CVE-2017-17899
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-17899
[3] https://security-tracker.debian.org/tracker/CVE-2017-17900
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-17900

In one case the code moved from subscriptions_info.php to
subscriptions/info.php, still decided to fill one bug report for the
four CVEs since set of fixes and affected versions are same.

If I was wrong on this regard, please clone the bug and adjust
affected versions as needed for the BTS.

Regards,
Salvatore

Bug#872724: pyasn1

[Vincent Bernat]

 ❦ 26 décembre 2017 07:23 +0100, Vincent Bernat  :

>> Do you expect one of us to upload or did you want to do that yourself
>> (both are fine for me)? 
>
> I didn't read the bug history. I'll upload a new version shortly,
> without doing a transition because we don't usually do that with Python
> and nobody strongly disapproved me.

So, it's uploaded in experimental as it breaks pysnmp4. I'll look into
uploading a newer version for this one soon.
-- 
Don't sacrifice clarity for small gains in "efficiency".
- The Elements of Programming Style (Kernighan & Plauger)


signature.asc
Description: PGP signature

Bug#872724: pyasn1

[Timo Aaltonen]

On 26.12.2017 08:23, Vincent Bernat wrote:
>  ❦ 26 décembre 2017 07:21 +0100, Vincent Bernat  :
> 
>> Do you expect one of us to upload or did you want to do that yourself
>> (both are fine for me)? 
> 
> I didn't read the bug history. I'll upload a new version shortly,
> without doing a transition because we don't usually do that with Python
> and nobody strongly disapproved me.

Thanks! Yeah I don't think a transition is needed, just an update to
python-pyasn1-modules too.

Bug#885320: dolibarr: CVE-2017-14238 CVE-2017-14239 CVE-2017-14240 CVE-2017-14241

[Salvatore Bonaccorso]

Source: dolibarr
Version: 3.5.5+dfsg1-1
Severity: grave
Tags: patch security upstream

Hi,

the following vulnerabilities were published for dolibarr, filling
only one bug for the four CVEs since afaict the common set of
affectedversions to go back to at least 3.5.5+dfsg1-1.

CVE-2017-14238[0]:
| SQL injection vulnerability in admin/menus/edit.php in Dolibarr ERP/CRM
| version 6.0.0 allows remote attackers to execute arbitrary SQL commands
| via the menuId parameter.

CVE-2017-14239[1]:
| Multiple cross-site scripting (XSS) vulnerabilities in Dolibarr ERP/CRM
| 6.0.0 allow remote authenticated users to inject arbitrary web script
| or HTML via the (1) CompanyName, (2) CompanyAddress, (3) CompanyZip,
| (4) CompanyTown, (5) Fax, (6) EMail, (7) Web, (8) ManagingDirectors,
| (9) Note, (10) Capital, (11) ProfId1, (12) ProfId2, (13) ProfId3, (14)
| ProfId4, (15) ProfId5, or (16) ProfId6 parameter to
| htdocs/admin/company.php.

CVE-2017-14240[2]:
| There is a sensitive information disclosure vulnerability in
| document.php in Dolibarr ERP/CRM version 6.0.0 via the file parameter.

CVE-2017-14241[3]:
| Cross-site scripting (XSS) vulnerability in Dolibarr ERP/CRM 6.0.0
| allows remote authenticated users to inject arbitrary web script or
| HTML via the Title parameter to htdocs/admin/menus/edit.php.

If you fix the vulnerabilities please also make sure to include the
CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-14238
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-14238
[1] https://security-tracker.debian.org/tracker/CVE-2017-14239
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-14239
[2] https://security-tracker.debian.org/tracker/CVE-2017-14240
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-14240
[3] https://security-tracker.debian.org/tracker/CVE-2017-14241
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-14241
[4] 
https://github.com/Dolibarr/dolibarr/commit/d26b2a694de30f95e46ea54ea72cc54f0d38e548

Regards,
Salvatore

Bug#885319: dolibarr: CVE-2017-14242: SQL injection vulnerability in don/list.php

[Salvatore Bonaccorso]

Source: dolibarr
Version: 3.5.5+dfsg1-1
Severity: important
Tags: patch security upstream

Hi,

the following vulnerability was published for dolibarr.

CVE-2017-14242[0]:
| SQL injection vulnerability in don/list.php in Dolibarr version 6.0.0
| allows remote attackers to execute arbitrary SQL commands via the
| statut parameter.

The code in question was moved several times around e.g. from
htdocs/compta/dons/list.php to htdocs/donations/list.php, then to the
dons directory.

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-14242
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-14242

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#885318: systemd kills X or freezes it when logging out from last opened tty

[Nekki Nekki]

Package: systemd
Version: 236-1
Severity: critical

Dear maintainers,

When using startx (no DM enabled) I suspect that systemd logs me out from
my X session
if it doesn't freezes it. I try to explain: I login in my openbox session
on tty1 using
startx, and in tty2 I run some program, say 'moc'. When I logout from tty2,
I get immediately
switched to tty1 and logged out from my openbox session. That is what
happens in my Sid guest.
I have same problem in my Sid host, but instead of being logged out from my
openbox session,
I get switched to it being in frozen state (Iget switched to tty1 and I get
my openbox session
frozen) and I am forced to use 'reisub'.
Note that:
1. if I don't 'exit' my tty2 session, I can switch between tty1 (openbox
session) and tty2,
or any other Console, just fine.
2. if I use a DM (I use wdm), I have no problems at all.
3. I sent this bug report from my Sid guest.

Please, let me know if you need more info/details.

Cheers,
Awtul

-- Package-specific info:

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

Kernel: Linux 4.14.0-2-amd64 (SMP w/1 CPU core)
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8),
LANGUAGE=es_ES:es (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages systemd depends on:
ii  adduser 3.116
ii  libacl1 2.2.52-3+b1
ii  libapparmor12.11.1-4
ii  libaudit1   1:2.8.2-1
ii  libblkid1   2.30.2-0.1
ii  libc6   2.25-5
ii  libcap2 1:2.25-1.2
ii  libcryptsetup4  2:1.7.5-1
ii  libgcrypt20 1.8.1-4
ii  libgpg-error0   1.27-5
ii  libidn111.33-2.1
ii  libip4tc0   1.6.1-2+b1
ii  libkmod224-1
ii  liblz4-10.0~r131-2+b1
ii  liblzma55.2.2-1.3
ii  libmount1   2.30.2-0.1
ii  libpam0g1.1.8-3.6
ii  libseccomp2 2.3.1-2.1
ii  libselinux1 2.7-2
ii  libsystemd0 236-1
ii  mount   2.30.2-0.1
ii  procps  2:3.3.12-3
ii  util-linux  2.30.2-0.1

Versions of packages systemd recommends:
ii  dbus1.12.2-1
ii  libpam-systemd  236-1

Versions of packages systemd suggests:
ii  policykit-10.105-18
pn  systemd-container  

Versions of packages systemd is related to:
pn  dracut   
ii  initramfs-tools  0.130
ii  udev 236-1

-- Configuration Files:
/etc/systemd/system.conf changed:
[Manager]
ShowStatus=yes


-- no debconf information


.xsession-errors
Description: Binary data
[  2755.743] 
X.Org X Server 1.19.5
Release Date: 2017-10-12
[  2755.746] X Protocol Version 11, Revision 0
[  2755.747] Build Operating System: Linux 4.9.0-4-amd64 x86_64 Debian
[  2755.748] Current Operating System: Linux debian-sid 4.14.0-2-amd64 #1 SMP Debian 4.14.7-1 (2017-12-22) x86_64
[  2755.748] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.14.0-2-amd64 root=UUID=c10d2d0f-d956-44c6-93cc-2009ef1af9ae ro quiet fbcon=scrollback:1024k
[  2755.751] Build Date: 16 October 2017  12:28:38PM
[  2755.752] xorg-server 2:1.19.5-1 (https://www.debian.org/support) 
[  2755.753] Current version of pixman: 0.34.0
[  2755.755] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[  2755.755] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[  2755.761] (==) Log file: "/home/debian/.local/share/xorg/Xorg.0.log", Time: Mon Dec 25 21:02:22 2017
[  2755.762] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[  2755.762] (==) No Layout section.  Using the first Screen section.
[  2755.762] (==) No screen section available. Using defaults.
[  2755.762] (**) |-->Screen "Default Screen Section" (0)
[  2755.762] (**) |   |-->Monitor ""
[  2755.763] (==) No monitor specified for screen "Default Screen Section".
	Using a default monitor configuration.
[  2755.763] (==) Automatically adding devices
[  2755.763] (==) Automatically enabling devices
[  2755.763] (==) Automatically adding GPU devices
[  2755.763] (==) Max clients allowed: 256, resource mask: 0x1f
[  2755.763] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[  2755.763] 	Entry deleted from font path.
[  2755.763] (==) FontPath set to:
	/usr/share/fonts/X11/misc,
	/usr/share/fonts/X11/100dpi/:unscaled,
	/usr/share/fonts/X11/75dpi/:unscaled,
	/usr/share/fonts/X11/Type1,
	/usr/share/fonts/X11/100dpi,
	/usr/share/fonts/X11/75dpi,
	built-ins
[  2755.763] (==) ModulePath set to "/usr/lib/xorg/modules"
[  2755.763] (II) The server relies on udev to provide the list of input devices.
	If no devices become available, reconfigure udev or disable AutoAddDevices.
[  2755.763] (II) Loader magic: 0x559d6b743de0
[  2755.763] (II) Module ABI versions:
[  2755.763] 	X.Org ANSI C Emulation: 0.4
[  2755.763] 	X.Org Video Driver: 23.0
[  2755.763] 	X.Org XInput driver : 

Bug#885317: ITP: golang-github-influxdata-yamux -- Golang connection multiplexing library

[Alexandre Viau]

Package: wnpp
Severity: wishlist
Owner: Alexandre Viau 

* Package name: golang-github-influxdata-yamux
  Version : 0.0~git20171107.1f58ded-1
  Upstream Author : InfluxData
* URL : https://github.com/influxdata/yamux
* License : TODO
  Programming Lang: Go
  Description : Golang connection multiplexing library

 Yamux Yamux (Yet another Multiplexer) is a multiplexing library for
 Golang.  It relies on an underlying connection to provide reliability and
 ordering, such as TCP or Unix domain sockets, and provides stream-oriented
 multiplexing. It is inspired by SPDY but is not interoperable with it.

This is needed for influxdb

-- 
Alexandre Viau
av...@debian.org



signature.asc
Description: OpenPGP digital signature

Bug#885315: ITP: golang-github-influxdata-yarpc -- Yet Another RPC for Go

[Alexandre Viau]

Package: wnpp
Severity: wishlist
Owner: Alexandre Viau 

* Package name: golang-github-influxdata-yarpc
  Version : 0.0~git20170928.036268c-1
  Upstream Author : InfluxData
* URL : https://github.com/influxdata/yarpc
* License : TODO
  Programming Lang: Go
  Description : Yet Another RPC for Go

 yarpc yarpc is Yet Another RPC package for Go.

This is needed for influxdb

-- 
Alexandre Viau
av...@debian.org



signature.asc
Description: OpenPGP digital signature

Bug#885316: ITP: golang-github-influxdata-influxql -- Package influxql implements a parser for the InfluxDB query language.

[Alexandre Viau]

Package: wnpp
Severity: wishlist
Owner: Alexandre Viau 

* Package name: golang-github-influxdata-influxql
  Version : 0.0~git20171219.851636b-1
  Upstream Author : InfluxData
* URL : https://github.com/influxdata/influxql
* License : TODO
  Programming Lang: Go
  Description : Package influxql implements a parser for the
InfluxDB query language.

 The Influx Query Language SpecificationIntroduction This is a reference
 for the Influx Query Language ("InfluxQL").
 .
 InfluxQL is a SQL-like query language for interacting with InfluxDB.
 It has been lovingly crafted to feel familiar to those coming from other
 SQL or SQL-like environments while providing features specific to storing
 and analyzing time series data.  Notation The syntax is specified using
 Extended Backus-Naur Form ("EBNF").  EBNF is the same notation used in
 the Go (http://golang.org) programming language specification, which
 can be found here (https://golang.org/ref/spec).  Not so coincidentally,
 InfluxDB is written in Go.

Needed for influxdb, duh.

-- 
Alexandre Viau
av...@debian.org



signature.asc
Description: OpenPGP digital signature

Bug#872724: pyasn1

[Vincent Bernat]

 ❦ 26 décembre 2017 07:21 +0100, Vincent Bernat  :

> Do you expect one of us to upload or did you want to do that yourself
> (both are fine for me)? 

I didn't read the bug history. I'll upload a new version shortly,
without doing a transition because we don't usually do that with Python
and nobody strongly disapproved me.
-- 
Hell is empty and all the devils are here.
-- Wm. Shakespeare, "The Tempest"


signature.asc
Description: PGP signature

Bug#872724: pyasn1

[Vincent Bernat]

 ❦ 24 décembre 2017 22:25 +0200, Timo Aaltonen  :

> On PyPy, though, it always raises TypeError.  Before looking for
> alternatives, please take a moment to read the following explanation as
> to why it is the case.  What you are looking for may not be possible.
>
> A memory profiler using this function is most likely to give results
> inconsistent with reality on PyPy.  It would be possible to have
> sys.getsizeof() return a number (with enough work), but that may or
> may not represent how much memory the object uses.  It doesn't even
> make really sense to ask how much *one* object uses, in isolation
> with the rest of the system.  For example, instances have maps,
> which are often shared across many instances; in this case the maps
> would probably be ignored by an implementation of sys.getsizeof(),
> but their overhead is important in some cases if they are many
> instances with unique maps.  Conversely, equal strings may share
> their internal string data even if they are different objects---or
> empty containers may share parts of their internals as long as they
> are empty.  Even stranger, some lists create objects as you read
> them; if you try to estimate the size in memory of range(10**6) as
> the sum of all items' size, that operation will by itself create one
> million integer objects that never existed in the first place.
>
> 
>
> How to proceed from here?

Upstream of pyasn1 is responsive. I can copy-paste your text in a pull
request making "TypeError" an acceptable result. In the meantime, the
test can be patched on Debian.

Do you expect one of us to upload or did you want to do that yourself
(both are fine for me)? 
-- 
Anyone who has had a bull by the tail knows five or six more things
than someone who hasn't.
-- Mark Twain


signature.asc
Description: PGP signature

Bug#883917: closed by Osamu Aoki <os...@debian.org> (Bug#883917: fixed in im-config 0.33-1)

[ian_bruce]

On Sat, 23 Dec 2017 13:39:06 +
"Debian Bug Tracking System"  wrote:

> #883917: im-config: doesn't offer UIM as an option
> 
> It has been closed by Osamu Aoki .

Now im-config offers both ibus and uim as input methods, but neither of
them actually work, even though they are both installed. That is, they
don't appear in the XFCE panel, as they used to, prior to whatever these
recent changes have been.


$ dpkg -l | grep ibus | egrep -v '(l|scr)ibus'
ii  gir1.2-ibus-1.0:amd64  1.5.14-3  amd64  Intelligent Input Bus - 
introspection data
ii  ibus   1.5.14-3  amd64  Intelligent Input Bus - 
core
ii  ibus-mozc  2.20.2673.102+dfsg-2  amd64  Mozc engine for IBus - 
Client of the Mozc input method
ii  libibus-1.0-5:amd641.5.14-3  amd64  Intelligent Input Bus - 
shared library

Bug#885314: SystemD fails to report fatal table-proc on OpenSMTPD

[Martin Hanson]

Package: opensmtpd
Version: 6.0.2p1-2

When OpenSMTPD fails to parse a table passwd file it responds with a fatal 
error:

This is done manually:

# smtpd -vvvd -f /etc/smtpd.conf
warn: table-passwd: invalid entry
warn: table-passwd: error parsing config file
warn: table-proc: imsg_read: Connection reset by peer
fatal: table-proc: exiting
warn: parent -> lka: pipe closed

If you try to start OpenSMTPD with SystemD, using the same configuration, it 
starts and doesn't report any problems:

# systemctl start smtpd
# systemctl status opensmtpd
● opensmtpd.service - LSB: opensmtpd Mail Transport Agent
   Loaded: loaded (/etc/init.d/opensmtpd; generated; vendor preset: enabled)
   Active: active (exited) since Tue 2017-12-26 06:39:36 CET; 2s ago
 Docs: man:systemd-sysv-generator(8)
  Process: 2249 ExecStop=/etc/init.d/opensmtpd stop (code=exited, 
status=0/SUCCESS)
  Process: 2274 ExecStart=/etc/init.d/opensmtpd start (code=exited, 
status=0/SUCCESS)

dec 26 06:39:37 serv1 smtpd[2281]: setup_done: pony[2285] done
dec 26 06:39:37 serv1 smtpd[2281]: setup_done: queue[2286] done
dec 26 06:39:37 serv1 smtpd[2286]: setup_proc: queue done
dec 26 06:39:37 serv1 smtpd[2285]: setup_proc: pony express done
dec 26 06:39:37 serv1 smtpd[2284]: setup_proc: lookup done
dec 26 06:39:37 serv1 smtpd[2281]: setup_done: scheduler[2287] done
dec 26 06:39:37 serv1 smtpd[2281]: smtpd: setup done
dec 26 06:39:37 serv1 smtpd[2287]: setup_proc: scheduler done
dec 26 06:39:37 serv1 smtpd[2283]: setup_proc: control done
dec 26 06:39:37 serv1 smtpd[2282]: setup_proc: klondike done

Hence, there is no reason to suspect any errors.

Using "ss" I discovered that OpenSMTPD wasn't listening on any ports and the 
journal reveals the same problem as with starting OpenSMTPD manually in 
debugging mode:

# journalctl -xe
-- Unit opensmtpd.service has finished shutting down.
dec 26 06:39:01 serv1 CRON[2265]: pam_unix(cron:session): session opened for 
user vmail by (uid=0)
dec 26 06:39:01 serv1 CRON[2266]: (vmail) CMD (  $PYTHON $INSTANCE/manage.py 
handle_mailbox_operations)
dec 26 06:39:01 serv1 cron[303]: cannot create temporary file 
/var/spool/smtpd/offline/1514266741.DLjSdC: Permission denied
dec 26 06:39:01 serv1 CRON[2265]: (vmail) MAIL (mailed 3758 bytes of output but 
got status 0x0045 from MTA
  )
dec 26 06:39:01 serv1 CRON[2265]: pam_unix(cron:session): session closed for 
user vmail
dec 26 06:39:36 serv1 systemd[1]: Starting LSB: opensmtpd Mail Transport 
Agent...
-- Subject: Unit opensmtpd.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit opensmtpd.service has begun starting up.
dec 26 06:39:36 serv1 smtpd[2280]: info: OpenSMTPD 6.0.2p1 starting
dec 26 06:39:36 serv1 opensmtpd[2274]: Starting MTA: opensmtpd.
dec 26 06:39:36 serv1 systemd[1]: Started LSB: opensmtpd Mail Transport Agent.
-- Subject: Unit opensmtpd.service has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit opensmtpd.service has finished starting up.
-- 
-- The start-up result is done.
dec 26 06:39:36 serv1 smtpd[2287]: setup_peer: scheduler -> control[2283] fd=12
dec 26 06:39:37 serv1 smtpd[2285]: setup_peer: pony express -> control[2283] 
fd=10
dec 26 06:39:37 serv1 smtpd[2284]: setup_peer: lookup -> control[2283] fd=9
dec 26 06:39:37 serv1 smtpd[2283]: setup_peer: control -> klondike[2282] fd=8
dec 26 06:39:37 serv1 smtpd[2282]: setup_peer: klondike -> control[2283] fd=7
dec 26 06:39:37 serv1 smtpd[2286]: setup_peer: queue -> control[2283] fd=11
dec 26 06:39:37 serv1 smtpd[2286]: setup_peer: queue -> pony express[2285] fd=12
dec 26 06:39:37 serv1 smtpd[2285]: setup_peer: pony express -> klondike[2282] 
fd=11
dec 26 06:39:37 serv1 smtpd[2286]: setup_peer: queue -> lookup[2284] fd=13
dec 26 06:39:37 serv1 smtpd[2285]: setup_peer: pony express -> lookup[2284] 
fd=12
dec 26 06:39:37 serv1 smtpd[2286]: setup_peer: queue -> scheduler[2287] fd=14
dec 26 06:39:37 serv1 smtpd[2284]: setup_peer: lookup -> pony express[2285] 
fd=10
dec 26 06:39:37 serv1 smtpd[2285]: setup_peer: pony express -> queue[2286] fd=13
dec 26 06:39:37 serv1 smtpd[2284]: setup_peer: lookup -> queue[2286] fd=11
dec 26 06:39:37 serv1 smtpd[2287]: setup_peer: scheduler -> queue[2286] fd=13
dec 26 06:39:37 serv1 smtpd[2283]: setup_peer: control -> lookup[2284] fd=9
dec 26 06:39:37 serv1 smtpd[2283]: setup_peer: control -> pony express[2285] 
fd=10
dec 26 06:39:37 serv1 smtpd[2283]: setup_peer: control -> queue[2286] fd=11
dec 26 06:39:37 serv1 smtpd[2283]: setup_peer: control -> scheduler[2287] fd=12
dec 26 06:39:37 serv1 smtpd[2282]: setup_peer: klondike -> pony express[2285] 
fd=8
dec 26 06:39:37 serv1 smtpd[2281]: setup_done: ca[2282] done
dec 26 06:39:37 serv1 smtpd[2281]: setup_done: control[2283] done
dec 26 06:39:37 serv1 smtpd[2281]: setup_done: lka[2284] done
dec 26 06:39:37 serv1 smtpd[2281]: setup_done: pony[2285] done
dec 26 06:39:37 serv1 smtpd[2281]: 

Bug#885313: lottanzb: Depends on unmaintained pygtk

[Jeremy Bicha]

Source: lottanzb
Version: 0.6-1
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster

pygtk is unmaintained upstream. It has not had a release since GNOME 3
was released in 2011.

The way forward is to port your app to use GObject Introspection
bindings.

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Buster release as we're going to
try to remove pygtk this cycle.

If you have any question don't hesitate to ask.

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#885312: key-mon: Depends on unmaintained pygtk

[Jeremy Bicha]

Source: key-mon
Version: 1.17-1
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster

pygtk is unmaintained upstream. It has not had a release since GNOME 3
was released in 2011.

The way forward is to port your app to use GObject Introspection
bindings.

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Buster release as we're going to
try to remove pygtk this cycle.

If you have any question don't hesitate to ask.

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#885310: jumpnbump: Depends on unmaintained pygtk

[Jeremy Bicha]

Source: gumpnbump
Version: 1.60-2
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster

pygtk is unmaintained upstream. It has not had a release since GNOME 3
was released in 2011.

The way forward is to port your app to use GObject Introspection
bindings.

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Buster release as we're going to
try to remove pygtk this cycle.

If you have any question don't hesitate to ask.

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#885311: keepnote: Depends on unmaintained pygtk

[Jeremy Bicha]

Source: keepnote
Version: 0.7.8-1.1
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster

pygtk is unmaintained upstream. It has not had a release since GNOME 3
was released in 2011.

The way forward is to port your app to use GObject Introspection
bindings.

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Buster release as we're going to
try to remove pygtk this cycle.

If you have any question don't hesitate to ask.

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#885309: jack-mixer: Depends on unmaintained pygtk

[Jeremy Bicha]

Source: jack-mixer
Version: 10-1
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster

pygtk is unmaintained upstream. It has not had a release since GNOME 3
was released in 2011.

The way forward is to port your app to use GObject Introspection
bindings.

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Buster release as we're going to
try to remove pygtk this cycle.

If you have any question don't hesitate to ask.

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#885308: idjc: Depends on unmaintained pygtk

[Jeremy Bicha]

Source: idjc
Version: 0.8.16-1
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster

pygtk is unmaintained upstream. It has not had a release since GNOME 3
was released in 2011.

The way forward is to port your app to use GObject Introspection
bindings.

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Buster release as we're going to
try to remove pygtk this cycle.

If you have any question don't hesitate to ask.

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#885306: hocr-gtk: Depends on unmaintained pygtk

[Jeremy Bicha]

Package: hocr-gtk
Version: 0.10.18-2
Severity: important
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster

pygtk is unmaintained upstream. It has not had a release since GNOME 3
was released in 2011.

The way forward is to port your app to use GObject Introspection
bindings.

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Buster release as we're going to
try to remove pygtk this cycle.

If you have any question don't hesitate to ask.

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#885307: ibus-sunpinyin: Depends on unmaintained pygtk

[Jeremy Bicha]

Source: ibus-sunpinyin
Version: 2.0.3-5
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster

pygtk is unmaintained upstream. It has not had a release since GNOME 3
was released in 2011.

The way forward is to port your app to use GObject Introspection
bindings.

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Buster release as we're going to
try to remove pygtk this cycle.

If you have any question don't hesitate to ask.

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#885302: gtklick: Depends on unmaintained pygtk

[Jeremy Bicha]

Source: gtklick
Version: 0.6.4-5
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster

pygtk is unmaintained upstream. It has not had a release since GNOME 3
was released in 2011.

The way forward is to port your app to use GObject Introspection
bindings.

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Buster release as we're going to
try to remove pygtk this cycle.

If you have any question don't hesitate to ask.

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#885303: gwakeonlan: Depends on unmaintained pygtk

[Jeremy Bicha]

Source: gwakeonlan
Version: 0.5.1-1.2
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster

pygtk is unmaintained upstream. It has not had a release since GNOME 3
was released in 2011.

The way forward is to port your app to use GObject Introspection
bindings.

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Buster release as we're going to
try to remove pygtk this cycle.

If you have any question don't hesitate to ask.

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#885304: hatari: Depends on unmaintained pygtk

[Jeremy Bicha]

Source: hatari
Version: 2.0.0+dfsg-4
Severity: important
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster

pygtk is unmaintained upstream. It has not had a release since GNOME 3
was released in 2011.

The way forward is to port your app to use GObject Introspection
bindings.

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Buster release as we're going to
try to remove pygtk this cycle.

If you have any question don't hesitate to ask.

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#885305: hijra: Depends on unmaintained pygtk

[Jeremy Bicha]

Source: hijra
Version: 0.4.1-1
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster

pygtk is unmaintained upstream. It has not had a release since GNOME 3
was released in 2011.

The way forward is to port your app to use GObject Introspection
bindings.

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Buster release as we're going to
try to remove pygtk this cycle.

If you have any question don't hesitate to ask.

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#885298: gquilt: Depends on unmaintained pygtk

[Jeremy Bicha]

Source: gquilt
Version: 0.25-5
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster

pygtk is unmaintained upstream. It has not had a release since GNOME 3
was released in 2011.

The way forward is to port your app to use GObject Introspection
bindings.

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Buster release as we're going to
try to remove pygtk this cycle.

If you have any question don't hesitate to ask.

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#885299: griffith: Depends on unmaintained pygtk

[Jeremy Bicha]

Source: griffith
Version: 0.13+20140313-1
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster

pygtk is unmaintained upstream. It has not had a release since GNOME 3
was released in 2011.

The way forward is to port your app to use GObject Introspection
bindings.

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Buster release as we're going to
try to remove pygtk this cycle.

If you have any question don't hesitate to ask.

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#885297: gpsd-clients: Depends on unmaintained pygtk

[Jeremy Bicha]

Package: gpsd-clients
Version: 3.17-3
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster

pygtk is unmaintained upstream. It has not had a release since GNOME 3
was released in 2011.

The way forward is to port your app to use GObject Introspection
bindings.

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Buster release as we're going to
try to remove pygtk this cycle.

If you have any question don't hesitate to ask.

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#885301: gtk-recordmydesktop: Depends on unmaintained pygtk

[Jeremy Bicha]

Source: gtk-recordmydesktop
Version: 0.3.8-4.1
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster

pygtk is unmaintained upstream. It has not had a release since GNOME 3
was released in 2011.

The way forward is to port your app to use GObject Introspection
bindings.

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Buster release as we're going to
try to remove pygtk this cycle.

If you have any question don't hesitate to ask.

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#885300: gtg: Depends on unmaintained pygtk

[Jeremy Bicha]

Source: gtg
Version: 0.3.1-4
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster

pygtk is unmaintained upstream. It has not had a release since GNOME 3
was released in 2011.

The way forward is to port your app to use GObject Introspection
bindings.

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Buster release as we're going to
try to remove pygtk this cycle.

If you have any question don't hesitate to ask.

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#885296: ITP: golang-go.uber-atomic -- Wrapper types for sync/atomic which enforce atomic access

[Alexandre Viau]

Package: wnpp
Severity: wishlist
Owner: Alexandre Viau 

* Package name: golang-go.uber-atomic
  Version : 1.3.1-1
  Upstream Author : Uber Golang
* URL : https://github.com/uber-go/atomic
* License : TODO
  Programming Lang: Go
  Description : Wrapper types for sync/atomic which enforce atomic
access

this is needed for influxdb

-- 
Alexandre Viau
av...@debian.org



signature.asc
Description: OpenPGP digital signature

Bug#885293: gnumeric-plugins-extra: Depends on unmaintained pygtk

[Jeremy Bicha]

Package: gnumeric-plugins-extra
Version: 1.12.35-1
Severity: important
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster

pygtk is unmaintained upstream. It has not had a release since GNOME 3
was released in 2011.

The way forward is to port your app to use GObject Introspection
bindings.

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Buster release as we're going to
try to remove pygtk this cycle.

If you have any question don't hesitate to ask.

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#885292: gmobilemedia: Depends on unmaintained pygtk

[Jeremy Bicha]

Source: gmobilemedia
Version: 0.4+dfsg-14
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster

pygtk is unmaintained upstream. It has not had a release since GNOME 3
was released in 2011.

The way forward is to port your app to use GObject Introspection
bindings.

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Buster release as we're going to
try to remove pygtk this cycle.

If you have any question don't hesitate to ask.

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#885294: gnuradio: Depends on unmaintained pygtk

[Jeremy Bicha]

Source: gnuradio
Version: 3.7.11-6
Severity: important
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster

pygtk is unmaintained upstream. It has not had a release since GNOME 3
was released in 2011.

The way forward is to port your app to use GObject Introspection
bindings.

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Buster release as we're going to
try to remove pygtk this cycle.

If you have any question don't hesitate to ask.

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#885295: gpodder: Depends on unmaintained pygtk

[Jeremy Bicha]

Source: gpodder
Version: 3.9.3-1
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster

pygtk is unmaintained upstream. It has not had a release since GNOME 3
was released in 2011.

The way forward is to port your app to use GObject Introspection
bindings.

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Buster release as we're going to
try to remove pygtk this cycle.

If you have any question don't hesitate to ask.

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#885288: OpenSMTPD cannot read passwd file: table-passwd: invalid entry

[Martin Hanson]

Package: opensmtpd-extras
Version: 5.7.1-3

I have installed opensmtpd and opensmtpd-extras on a fresh Debian Strech 
installation.

I have generated a password using the command:

# smtpctl encrypt

This is my OpenSMTPD configuration file:

---
# cat /etc/smtpd.conf
# This is the smtpd server system-wide configuration file.
# See smtpd.conf(5) for more information.

# The pki setup.
pki serv1.example.com certificate "/etc/ssl/serv1.example.com.crt"
pki serv1.example.com key "/etc/ssl/private/serv1.example.com.key"

# Tables used for domains, users, passwords and aliases.
table aliases file:/etc/mail/aliases
table domains file:/etc/mail/domains
table passwd passwd:/etc/mail/passwd
table virtuals file:/etc/mail/virtuals

# Ports to listen on.
listen on lo 
listen on enp0s3 port 25 tls pki serv1.example.com
listen on enp0s3 port 587 tls-require pki serv1.example.com auth 

# Allow local delivery.
accept from local for local alias  deliver to lmtp 
"/var/run/dovecot/lmtp" rcpt-to
# Allow virtual domains.
accept from any for domain  virtual  deliver to lmtp 
"/var/run/dovecot/lmtp" rcpt-to
# Allow outgoing emails.
accept from local for any relay
---

Now, I have tried several different setups in the password file, but no matter 
what I do OpenSMTPD cannot read the file:

---
# smtpd -vvvd -f /etc/smtpd.conf
...
warn: table-passwd: invalid entry
warn: table-passwd: error parsing config file
warn: table-proc: imsg_read: Connection reset by peer
fatal: table-proc: exiting
warn: parent -> lka: pipe closed
---

I have a running OpenBSD 6.2 server where I have copied the passwd file to 
Debian and tried with that, but I get the same error.

On my OpenBSD box the passwd file looks like this (following the exact example 
from the OpenSMTPD FAQ) and it's working on OpenBSD:

---
f...@example.com:$2b$10$iziy9n1wNjlcJ5Bf4wcd2OO3Mr8ssAIt/JZUmn9E6EdK2KMHlMfB6:
---

On Debian, using the same command to create the password creates another kind 
of string generated, but neither works anyway:

---
f...@example.com:$6$8PfdjgX6RXPbB7CB$NeSd4vYBXqj6SYIG3ke6RW2VlktZk4rdBWdx8o8dn7qx7ZKXliYoa/eRL7vUuo.Ayc8iBhQUYegx6sBFiY0Ht0:
---

I have tried with various settings like (password has been shortened):

---
f...@example.com:$6$8Pfdjg:
f...@example.com $6$8Pfdjg:
foo:$6$8Pfdjg:
foo $6$8Pfdjg:
f...@example.com:$6$8Pfdjg
f...@example.com $6$8Pfdjg
foo:$6$8Pfdjg
foo $6$8Pfdjg
foo
---

No matter what setup I use I get the same error.

I suspect something is wrong with the table-passwd filter?

Kind regards,
Martin

Bug#885287: gespeaker: Depends on unmaintained pygtk

[Jeremy Bicha]

Source: gespeaker
Version: 0.8.6-1
Severity: important
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster
X-Debbugs-CC: vch...@debian.org

pygtk is unmaintained upstream. It has not had a release since GNOME 3
was released in 2011.

The way forward is to port your app to use GObject Introspection
bindings.

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Buster release as we're going to
try to remove pygtk this cycle.

If you have any question don't hesitate to ask.

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#885285: : Depends on unmaintained pygtk

[Jeremy Bicha]

Source: geda-xgsch2pcb
Version: 0.1.3-3
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster

pygtk is unmaintained upstream. It has not had a release since GNOME 3
was released in 2011.

The way forward is to port your app to use GObject Introspection
bindings.

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Buster release as we're going to
try to remove pygtk this cycle.

If you have any question don't hesitate to ask.

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#885286: ITP: golang-go.uber-zap -- Blazing fast, structured, leveled logging in Go

[Alexandre Viau]

Package: wnpp
Severity: wishlist
Owner: Alexandre Viau 

* Package name: golang-go.uber-zap
  Version : 1.7.1+git20171031.f85c78b-1
  Upstream Author : Uber Golang
* URL : https://github.com/uber-go/zap
* License : Expat
  Programming Lang: Go
  Description : Blazing fast, structured, leveled logging in Go.

-- 
Alexandre Viau
av...@debian.org



signature.asc
Description: OpenPGP digital signature

Bug#885291: : Depends on unmaintained pygtk

[Jeremy Bicha]

Source: globs
Version: 0.2.0~svn50-4
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster

pygtk is unmaintained upstream. It has not had a release since GNOME 3
was released in 2011.

The way forward is to port your app to use GObject Introspection
bindings.

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Buster release as we're going to
try to remove pygtk this cycle.

If you have any question don't hesitate to ask.

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#885290: geximon: Depends on unmaintained pygtk

[Jeremy Bicha]

Source: geximon
Version: 0.7.7-2.1
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster

pygtk is unmaintained upstream. It has not had a release since GNOME 3
was released in 2011.

The way forward is to port your app to use GObject Introspection
bindings.

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Buster release as we're going to
try to remove pygtk this cycle.

If you have any question don't hesitate to ask.

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#885289: gimp: Depends on unmaintained pygtk

[Jeremy Bicha]

Source: gimp
Version: 2.8.20-1
Severity: important
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster

pygtk is unmaintained upstream. It has not had a release since GNOME 3
was released in 2011.

The way forward is to port your app to use GObject Introspection
bindings.

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Buster release as we're going to
try to remove pygtk this cycle.

If you have any question don't hesitate to ask.

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#885284: gbirthday: Depends on unmaintained pygtk

[Jeremy Bicha]

Source: gbirthday
Version: 0.6.10-0.1
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster

pygtk is unmaintained upstream. It has not had a release since GNOME 3
was released in 2011.

The way forward is to port your app to use GObject Introspection
bindings.

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Buster release as we're going to
try to remove pygtk this cycle.

If you have any question don't hesitate to ask.

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#885280: fslint: Depends on unmaintained pygtk

[Jeremy Bicha]

Source: fslint
Version: 2.44-2
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster
X-Debbugs-CC: f...@rolf.leggewie.biz

pygtk is unmaintained upstream. It has not had a release since GNOME 3
was released in 2011.

The way forward is to port your app to use GObject Introspection
bindings.

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Buster release as we're going to
try to remove pygtk this cycle.

If you have any question don't hesitate to ask.

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#885279: ffrenzy: Depends on unmaintained pygtk

[Jeremy Bicha]

Source: ffrenzy
Version: 1.0.2~svn20150731-1
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster

pygtk is unmaintained upstream. It has not had a release since GNOME 3
was released in 2011.

The way forward is to port your app to use GObject Introspection
bindings.

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Buster release as we're going to
try to remove pygtk this cycle.

If you have any question don't hesitate to ask.

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#885282: gameclock: Depends on unmaintained pygtk

[Jeremy Bicha]

Source: gameclock
Version: 5.1
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster

pygtk is unmaintained upstream. It has not had a release since GNOME 3
was released in 2011.

The way forward is to port your app to use GObject Introspection
bindings.

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Buster release as we're going to
try to remove pygtk this cycle.

If you have any question don't hesitate to ask.

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#885283: ganyremote: Depends on unmaintained pygtk

[Jeremy Bicha]

Source: ganyremote
Version: 6.3.3-1
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster

pygtk is unmaintained upstream. It has not had a release since GNOME 3
was released in 2011.

The way forward is to port your app to use GObject Introspection
bindings.

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Buster release as we're going to
try to remove pygtk this cycle.

If you have any question don't hesitate to ask.

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#885281: furiusisomount: Depends on unmaintained pygtk

[Jeremy Bicha]

Source: furiusisomount
Version: 0.11.3.1~repack1-1
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster

pygtk is unmaintained upstream. It has not had a release since GNOME 3
was released in 2011.

The way forward is to port your app to use GObject Introspection
bindings.

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Buster release as we're going to
try to remove pygtk this cycle.

If you have any question don't hesitate to ask.

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#885278: epoptes: Depends on unmaintained pygtk

[Jeremy Bicha]

Source: epoptes
Version: 0.5.10-2
Severity: important
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster

pygtk is unmaintained upstream. It has not had a release since GNOME 3
was released in 2011.

The way forward is to port your app to use GObject Introspection
bindings.

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Buster release as we're going to
try to remove pygtk this cycle.

If you have any question don't hesitate to ask.

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#885276: driconf: Depends on unmaintained pygtk

[Jeremy Bicha]

Source: driconf
Version: 0.9.1-4
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster
X-Debbugs-CC: vch...@debian.org

pygtk is unmaintained upstream. It has not had a release since GNOME 3
was released in 2011.

The way forward is to port your app to use GObject Introspection
bindings.

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Buster release as we're going to
try to remove pygtk this cycle.

If you have any question don't hesitate to ask.

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#885277: emma: Depends on unmaintained pygtk

[Jeremy Bicha]

Source: emma
Version: 0.6-5
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster

pygtk is unmaintained upstream. It has not had a release since GNOME 3
was released in 2011.

The way forward is to port your app to use GObject Introspection
bindings.

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Buster release as we're going to
try to remove pygtk this cycle.

If you have any question don't hesitate to ask.

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#885272: ITP: golang-go.pedge-lion -- Structured logging with Protocol Buffers

[Alexandre Viau]

Package: wnpp
Severity: wishlist
Owner: Alexandre Viau 

* Package name: golang-go.pedge-lion
  Version : 0.0~git20171203.2a81062-1
  Upstream Author : Peter Edge
* URL : https://github.com/peter-edge/lion-go
* License : Expat
  Programming Lang: Go
  Description : Structured logging with Protocol Buffers

This is needed for influxdb

-- 
Alexandre Viau
av...@debian.org



signature.asc
Description: OpenPGP digital signature

Bug#885270: d-rats: Depends on unmaintained pygtk

[Jeremy Bicha]

Source: d-rats
Version: 0.3.3-4
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster

pygtk is unmaintained upstream. It has not had a release since GNOME 3
was released in 2011.

The way forward is to port your app to use GObject Introspection
bindings.

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Buster release as we're going to
try to remove pygtk this cycle.

If you have any question don't hesitate to ask.

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#885273: diffuse: Depends on unmaintained pygtk

[Jeremy Bicha]

Source: diffuse
Version: 0.4.8-3
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster

pygtk is unmaintained upstream. It has not had a release since GNOME 3
was released in 2011.

The way forward is to port your app to use GObject Introspection
bindings.

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Buster release as we're going to
try to remove pygtk this cycle.

If you have any question don't hesitate to ask.

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#885275: disk-manager: Depends on unmaintained pygtk

[Jeremy Bicha]

Source: disk-manager
Version: 1.1.1-2
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster

pygtk is unmaintained upstream. It has not had a release since GNOME 3
was released in 2011.

The way forward is to port your app to use GObject Introspection
bindings.

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Buster release as we're going to
try to remove pygtk this cycle.

If you have any question don't hesitate to ask.

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#885271: dia-common: Depends on unmaintained pygtk

[Jeremy Bicha]

Package: dia-common
Version: 0.97.3+git20160930-7
Severity: important
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster

pygtk is unmaintained upstream. It has not had a release since GNOME 3
was released in 2011.

The way forward is to port your app to use GObject Introspection
bindings.

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Buster release as we're going to
try to remove pygtk this cycle.

If you have any question don't hesitate to ask.

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#885274: directoryassistant: Depends on unmaintained pygtk

[Jeremy Bicha]

Source: directoryassistant
Version: 2.0-1.1
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster

pygtk is unmaintained upstream. It has not had a release since GNOME 3
was released in 2011.

The way forward is to port your app to use GObject Introspection
bindings.

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Buster release as we're going to
try to remove pygtk this cycle.

If you have any question don't hesitate to ask.

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#885269: compizconfig-settings-manager: Depends on unmaintained pygtk

[Jeremy Bicha]

Package: compizconfig-settings-manager
Version: 1:0.9.13.0+16.10.20160818.2-5.1
Severity: important
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster

pygtk is unmaintained upstream. It has not had a release since GNOME 3
was released in 2011.

The way forward is to port your app to use GObject Introspection
bindings.

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Buster release as we're going to
try to remove pygtk this cycle.

If you have any question don't hesitate to ask.

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#885267: coccinelle: Depends on unmaintained pygtk

[Jeremy Bicha]

Source: coccinelle
Version: 1.0.4.deb-3
Severity: important
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster

pygtk is unmaintained upstream. It has not had a release since GNOME 3
was released in 2011.

The way forward is to port your app to use GObject Introspection
bindings.

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Buster release as we're going to
try to remove pygtk this cycle.

If you have any question don't hesitate to ask.

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#885268: comix: Depends on unmaintained pygtk

[Jeremy Bicha]

Source: comix
Version: 4.0.4-3
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster

pygtk is unmaintained upstream. It has not had a release since GNOME 3
was released in 2011.

The way forward is to port your app to use GObject Introspection
bindings.

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Buster release as we're going to
try to remove pygtk this cycle.

If you have any question don't hesitate to ask.

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#885265: chirp: Depends on unmaintained pygtk

[Jeremy Bicha]

Source: chirp
Version: 1:20170714-1
Severity: important
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster

pygtk is unmaintained upstream. It has not had a release since GNOME 3
was released in 2011.

The way forward is to port your app to use GObject Introspection
bindings.

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Buster release as we're going to
try to remove pygtk this cycle.

If you have any question don't hesitate to ask.

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#885266: claws-mail-python-plugin: Depends on unmaintained pygtk

[Jeremy Bicha]

Package: claws-mail-python-plugin
Version: 3.16.0-1
Severity: important
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster

pygtk is unmaintained upstream. It has not had a release since GNOME 3
was released in 2011.

The way forward is to port your app to use GObject Introspection
bindings.

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Buster release as we're going to
try to remove pygtk this cycle.

If you have any question don't hesitate to ask.

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#885263: caja-dropbox: Depends on unmaintained pygtk

[Jeremy Bicha]

Source: caja-dropbox
Version: 1.18.0-2
Severity: important
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster

pygtk is unmaintained upstream. It has not had a release since GNOME 3
was released in 2011.

The way forward is to port your app to use GObject Introspection
bindings.

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Buster release as we're going to
try to remove pygtk this cycle.

If you have any question don't hesitate to ask.

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#885264: childsplay: Depends on unmaintained pygtk

[Jeremy Bicha]

Source: childsplay
Version: 2.6.5+dfsg-1
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster

pygtk is unmaintained upstream. It has not had a release since GNOME 3
was released in 2011.

The way forward is to port your app to use GObject Introspection
bindings.

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Buster release as we're going to
try to remove pygtk this cycle.

If you have any question don't hesitate to ask.

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#885262: buxon: Depends on unmaintained pygtk

[Jeremy Bicha]

Source: buxon
Version: 0.0.5-5
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster

pygtk is unmaintained upstream. It has not had a release since GNOME 3
was released in 2011.

The way forward is to port your app to use GObject Introspection
bindings.

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Buster release as we're going to
try to remove pygtk this cycle.

If you have any question don't hesitate to ask.

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#885261: bleachbit: Depends on unmaintained pygtk

[Jeremy Bicha]

Source: bleachbit
Version: 1.15-2
Severity: important
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster

pygtk is unmaintained upstream. It has not had a release since GNOME 3
was released in 2011.

The way forward is to port your app to use GObject Introspection
bindings.

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Buster release as we're going to
try to remove pygtk this cycle.

If you have any question don't hesitate to ask.

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#885260: ITP: golang-go.pedge-env -- Structured handling of environment variables in Go

[Alexandre Viau]

Package: wnpp
Severity: wishlist
Owner: Alexandre Viau 

* Package name: golang-go.pedge-env
  Version : 0.0~git20171203.5f5a7de-1
  Upstream Author : Peter Edge
* URL : https://github.com/peter-edge/env-go
* License : Expat
  Programming Lang: Go
  Description : Structured handling of environment variables in Go


-- 
Alexandre Viau
av...@debian.org



signature.asc
Description: OpenPGP digital signature

Bug#885259: arandr: Depends on unmaintained pygtk

[Jeremy Bicha]

Source: arandr
Version: 0.1.9-2
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster

pygtk is unmaintained upstream. It has not had a release since GNOME 3
was released in 2011.

The way forward is to port your app to use GObject Introspection
bindings.

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Buster release as we're going to
try to remove pygtk this cycle.

If you have any question don't hesitate to ask.

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#885258: apoo: Depends on unmaintained pygtk

[Jeremy Bicha]

Source: apoo
Version: 2.2-4
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster

pygtk is unmaintained upstream. It has not had a release since GNOME 3
was released in 2011.

The way forward is to port your app to use GObject Introspection
bindings.

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Buster release as we're going to
try to remove pygtk this cycle.

If you have any question don't hesitate to ask.

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#885256: activity-log-manager: Depends on unmaintained pygtk

[Jeremy Bicha]

Source: activity-log-manager
Version: 0.8.0-1.2
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster

pygtk is unmaintained upstream. It has not had a release since
GNOME 3 was released in 2011.

The way forward is to port your app to use GObject Introspection
bindings.

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Buster release as we're going to
try to remove pygtk this cycle.

If you have any question don't hesitate to ask.

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#885257: agtl: Depends on unmaintained pygtk

[Jeremy Bicha]

Source: agtl
Version: 0.8.0.3-1.1
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster

pygtk is unmaintained upstream. It has not had a release since GNOME 3
was released in 2011.

The way forward is to port your app to use GObject Introspection
bindings.

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Buster release as we're going to
try to remove pygtk this cycle.

If you have any question don't hesitate to ask.

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#885242: libnitrokey: FTBFS (32-bit): symbols not as expected

[Scott Kitterman]

Once I get all the build logs I'll update it later this week.

Scott K

On December 25, 2017 10:20:57 PM EST, "Aaron M. Ucko"  wrote:
>Source: libnitrokey
>Version: 3.1-1
>Severity: important
>Justification: fails to build from source
>
>Builds of libnitrokey for 32-bit architectures such as i386 have been
>failing because the library's symbols differ somewhat from the
>expectations in libnitrokey3.symbols, as detailed at
>
>https://buildd.debian.org/status/logs.php?pkg=libnitrokey=3.1-1
>
>Could you please take a look and account for this variation (bearing
>in mind that the details may turn out to be architecture-dependent)?
>
>Thanks!

Bug#825095: [Python-modules-team] Bug#825095: Bug#825095: python-backports-shutil-get-terminal-size: clashes over backports/__init__.py with python-backports.ssl-match-hostname

[Sandro Tosi]

> The page:
> https://tracker.debian.org/pkg/python-backports-shutil-get-terminal-size
>
> says 1.0.0-3~bpo8+1 is in old-bbpo, 1.0.0-3 is in stable, and 1.0.0-4 is
> in testing and unstable.
>
> The changelog is:
> python-backports-shutil-get-terminal-size (1.0.0-4) unstable; urgency=medium
>
>   * Fix a typo in the substvar depends (Closes: #884687)
>   * Refresh packaging:
> - Use https in d/copyright's Format.
> - Bump dh compat to 10.
> - Bump d/watch to version 4.
> - Bump std-ver to 4.1.2.0.
> - Add lintian override for a silly warning.
>
>  -- Julien Puydt   Tue, 19 Dec 2017 00:30:44 +0100
>
> python-backports-shutil-get-terminal-size (1.0.0-3) unstable; urgency=medium
>
>   * Declare Breaks with old python-backports.ssl-match-hostname so
> upgrading works. (Closes: #825095)
>
>  -- Julien Puydt   Thu, 28 Jul 2016 11:48:50 +0200
>
> python-backports-shutil-get-terminal-size (1.0.0-2) unstable; urgency=medium
>
>   * Fixed file conflict with other python-backports-* packages. (Closes:
> 825095)
>   * Fixed Vcs-* fields.
>
>  -- Julien Puydt   Thu, 21 Jul 2016 13:13:26 +0200
>
> python-backports-shutil-get-terminal-size (1.0.0-1) unstable; urgency=medium
>
>   * Initial release. (Closes: #824984)
>
>  -- Julien Puydt   Sun, 22 May 2016 16:52:23 +0200
>
>

i'm not sure why you're quoting this, not really relevant.

> Where did you get that 1.0.0-1 from?

that's just the version this bug was originally reported against,
unclear why you're surprised

> It's outrageously outdated... and
> that is why you still see the problem!

no. this was correctly addressed in -5

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

Bug#885255: ITP: golang-github-apex-log -- Structured logging package for Go

[Alexandre Viau]

Package: wnpp
Severity: wishlist
Owner: Alexandre Viau 

* Package name: golang-github-apex-log
  Version : 1.0.0-1
  Upstream Author : Apex
* URL : https://github.com/apex/log
* License : Expat
  Programming Lang: Go
  Description : Structured logging package for Go.

 Structured logging for golang
 .
 Package log implements a simple structured logging API inspired by
 Logrus, designed with centralization in mind.

This is needed for influxdb

-- 
Alexandre Viau
av...@debian.org



signature.asc
Description: OpenPGP digital signature

Bug#885254: bluewho: Depends on deprecated pygtk

[Jeremy Bicha]

Package: bluewho
Version: 0.1-2
Severity: serious
Tags: sid buster
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk

pygtk is unmaintained upstream. It has not had a release since
GNOME 3 was released in 2011.

The way forward is to port your app to use GObject Introspection
bindings.

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Buster release as we're going to
try to remove pygtk this cycle.

If you have any question don't hesitate to ask.

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#885253: ITP: golang-github-tj-go-spin -- Terminal spinner package for Golang

[Alexandre Viau]

Package: wnpp
Severity: wishlist
Owner: Alexandre Viau 

* Package name: golang-github-tj-go-spin
  Version : 1.1.0-1
  Upstream Author : TJ Holowaychuk
* URL : https://github.com/tj/go-spin
* License : Expast
  Programming Lang: Go
  Description : Terminal spinner package for Golang

 go-spin Little terminal spinner lib.

this is needed for influxdb

-- 
Alexandre Viau
av...@debian.org



signature.asc
Description: OpenPGP digital signature

Bug#885252: yahtzeesharp: Build-Depends on libart2.0-cil-dev

[Jeremy Bicha]

From c5536ddbc2b7ed00a901413a452593b4edb4648a Mon Sep 17 00:00:00 2001
From: Jeremy Bicha 
Date: Mon, 25 Dec 2017 20:28:38 -0500
Subject: [PATCH 1/8] Drop unnecessary libart depends

---
 debian/control  |  2 +-
 debian/patches/03_drop_libart_depends.patch | 33 +
 debian/patches/series   |  1 +
 3 files changed, 35 insertions(+), 1 deletion(-)
 create mode 100644 debian/patches/03_drop_libart_depends.patch

diff --git a/debian/control b/debian/control
index 9410ae9..2c73845 100644
--- a/debian/control
+++ b/debian/control
@@ -6,7 +6,7 @@ Uploaders: Stefan Ebner 
 Build-Depends: debhelper (>= 7.0.50), quilt (>= 0.46-7~),
  cli-common-dev (>= 0.7), imagemagick
 Build-Depends-Indep: mono-devel (>= 2.4.2.3),
- libglib2.0-cil-dev, libgtk2.0-cil-dev, libart2.0-cil-dev
+ libglib2.0-cil-dev, libgtk2.0-cil-dev
 Standards-Version: 3.8.3
 Homepage: http://www.brdstudio.net/yahtzeesharp/
 Vcs-Git: git://git.debian.org/pkg-cli-apps/packages/yahtzeesharp.git
diff --git a/debian/patches/03_drop_libart_depends.patch b/debian/patches/03_drop_libart_depends.patch
new file mode 100644
index 000..6476dc4
--- /dev/null
+++ b/debian/patches/03_drop_libart_depends.patch
@@ -0,0 +1,33 @@
+From: Jeremy Bicha 
+Date: Mon, 25 Dec 2017 20:27:14 -0500
+Subject: Drop unnecessary libart depends
+
+---
+ YahtzeeSharp/Makefile.am | 1 -
+ configure.ac | 1 -
+ 2 files changed, 2 deletions(-)
+
+diff --git a/YahtzeeSharp/Makefile.am b/YahtzeeSharp/Makefile.am
+index e31bce9..fb14770 100644
+--- a/YahtzeeSharp/Makefile.am
 b/YahtzeeSharp/Makefile.am
+@@ -133,7 +133,6 @@ REFERENCES =  \
+ 	System.Data \
+ 	System \
+ 	System.Xml \
+-	$(ART_SHARP_20_LIBS) \
+ 	$(GTK_SHARP_20_LIBS) \
+ 	$(GLIB_SHARP_20_LIBS)
+ 
+diff --git a/configure.ac b/configure.ac
+index e8bf8c1..781f965 100644
+--- a/configure.ac
 b/configure.ac
+@@ -46,7 +46,6 @@ fi
+ 
+ dnl package checks, common for all configs
+ PKG_CHECK_MODULES([GLIB_SHARP_20], [glib-sharp-2.0])
+-PKG_CHECK_MODULES([ART_SHARP_20], [art-sharp-2.0])
+ PKG_CHECK_MODULES([GTK_SHARP_20], [gtk-sharp-2.0])
+ 
+ dnl package checks, per config
diff --git a/debian/patches/series b/debian/patches/series
index ab66544..562e618 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1,2 +1,3 @@
 01_fix_build_system
 02_fix_desktop_file
+03_drop_libart_depends.patch
-- 
2.14.1

From 16b16db0115b1f96bc4e7486529b1d522b5c1d7b Mon Sep 17 00:00:00 2001
From: Jeremy Bicha 
Date: Mon, 25 Dec 2017 22:42:03 -0500
Subject: [PATCH 2/8] Switch to 3.0 (quilt)

---
 debian/README.source | 57 
 debian/control   |  2 +-
 debian/rules |  7 +--
 debian/source/format |  1 +
 4 files changed, 3 insertions(+), 64 deletions(-)
 delete mode 100644 debian/README.source
 create mode 100644 debian/source/format

diff --git a/debian/README.source b/debian/README.source
deleted file mode 100644
index 8646078..000
--- a/debian/README.source
+++ /dev/null
@@ -1,57 +0,0 @@
-This package uses quilt to manage all modifications to the upstream
-source.  Changes are stored in the source package as diffs in
-debian/patches and applied during the build.
-
-To configure quilt to use debian/patches instead of patches, you want
-either to export QUILT_PATCHES=debian/patches in your environment
-or use this snippet in your ~/.quiltrc:
-
-for where in ./ ../ ../../ ../../../ ../../../../ ../../../../../; do
-if [ -e ${where}debian/rules -a -d ${where}debian/patches ]; then
-export QUILT_PATCHES=debian/patches
-fi
-done
-
-To get the fully patched source after unpacking the source package, cd to
-the root level of the source package and run:
-
-quilt push -a
-
-The last patch listed in debian/patches/series will become the current
-patch.
-
-To add a new set of changes, first run quilt push -a, and then run:
-
-quilt new 
-
-where  is a descriptive name for the patch, used as the filename in
-debian/patches.  Then, for every file that will be modified by this patch,
-run:
-
-quilt add 
-
-before editing those files.  You must tell quilt with quilt add what files
-will be part of the patch before making changes or quilt will not work
-properly.  After editing the files, run:
-
-quilt refresh
-
-to save the results as a patch.
-
-Alternately, if you already have an external patch and you just want to
-add it to the build system, run quilt push -a and then:
-
-quilt import -P  /path/to/patch
-quilt push -a
-
-(add -p 0 to quilt import if needed).  as above is the filename to
-use in debian/patches.  The last quilt push -a will apply the patch to
-make sure it works properly.
-
-To remove an existing patch from the list of patches that will be applied,
-run:
-
-quilt delete 
-
-You may need to run quilt pop -a to unapply patches first 

Bug#885249: yoshimi: FTBFS on hurd-i386: PATH_MAX undeclared

[Aaron M. Ucko]

Source: yoshimi
Version: 1.5.6-2
Severity: important
Tags: upstream
Justification: fails to build from source
User: debian-h...@lists.debian.org
Usertags: hurd-i386

Builds of yoshimi for hurd-i386 (admittedly not a release
architecture) have been failing:

  /<>/src/Misc/MiscFuncs.cpp: In member function 
'std::__cxx11::string MiscFuncs::localPath(std::__cxx11::string)':
  /<>/src/Misc/MiscFuncs.cpp:343:29: error: 'PATH_MAX' was not 
declared in this scope

The Hurd notoriously has no static PATH_MAX.  Best practice is to
accommodate whatever you actually encounter (with the help of, e.g.,
the GNU libc extension get_current_dir_name); alternatively, you can
look up _PC_PATH_MAX via pathconf or supply a fallback constant
(traditionally 4096).

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

Bug#885250: shared-mime-info: include filename and line in warning "Unknown media type in type 'all/all'"

[Paul Wise]

Package: shared-mime-info
Version: 1.9-2
Severity: normal
Usertags

During many different upgrades I get the warning below. I cannot easily
file bug reports about these warnings because the warning does not
mention which file is causing the warning.

Processing triggers for shared-mime-info (1.9-2) ...
Unknown media type in type 'all/all'
Unknown media type in type 'all/allfiles'

This style of warning is more actionable because I can file bugs:

Processing triggers for shared-mime-info (1.9-2) ...
Unknown media type in type 'all/all' in /usr/share/mime/packages/kde.xml:1790
Unknown media type in type 'all/allfiles' in 
/usr/share/mime/packages/kde.xml:1848

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

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

Versions of packages shared-mime-info depends on:
ii  libc6 2.25-5
ii  libglib2.0-0  2.54.1-1
ii  libxml2   2.9.4+dfsg1-5.2

shared-mime-info recommends no packages.

shared-mime-info suggests no packages.

-- no debconf information

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#885252: yahtzeesharp: Build-Depends on libart2.0-cil-dev

[Jeremy Bicha]

Source: yahtzeesharp
Version: 1.1-6
Severity: serious
Tags: patch pending
X-Debbugs-CC: seb...@ubuntu.com

yahtzeesharp Build-Depends on libart2.0-cil-dev, but libart2.0-cil-dev
will be removed from Debian soon because it is an old unmaintained
GNOME 2 library. See the announcement from the Debian GNOME team [1].

Fortunately, it looks like yahtzeesharp doesn't actually need that
library. In my follow-up email, I will attach a series of git patches
you can apply to fix this issue, build with autoreconf and modernize
the packaging a bit.

I am uploading a NMU now with these patches to DELAYED/15. Please let
me know if I should wait longer or upload sooner.

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

Thanks,
Jeremy Bicha

Bug#885241: glade: Gtypes mangled when packed in pointers in glade-base-editor

[William Panlener]

Package: glade
Version: 3.20.2-1
Followup-For: Bug #885241

Dear Maintainer,

Dear Maintainer,

   (Unmangled message)

   When attempting to add a cell renderer to a GTKTreeViewColumn, it was
discovered that this feature is broken in glade.

   To reproduce: Add a GTKTreeView to a GTKWindow in glade.  Right click the
GTKTreeView and select "Edit" in the popup window. In the Hierarchy pane, click
the + (plus) icon to add a new GTKTreeViewColumn. Right click the new column
and choose "Add child Text" from the popup window.

   It is expected that a GTKCellRendererText object would appear as a child of
the GTKTreeViewColumn, but instead, nothing happens. Other buggy behavior can
be seen in this same Hierarchy pane such as occasional segfaults when removing
columns.

   After debugging, it seems that this behavior and probable buggy behavior
with other GTK+ plugins using the glade-base-editor can be attributed to
mangling of GType values that occurs when packing these values into gints.
GType is an 8-byte unsigned value while gint is a signed 4 byte value (at least
on amd64).

   These patches were tested on a backport of glade from unstable (3.20.2-1) to
stretch with libglib-dev and debhelper build-dep versions relaxed to meet those
in stretch, the behavior bug is also present in the stable package (3.20.0-2)
and appears to be present upstream (untested but apparent in source and
unmentioned in Changelog).

   The patch consists of a macro wrapper to pack GTypes in a larger integer
type and a test to preempt regression. Ideally, most of this would be provided
by glib.



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

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

Versions of packages glade depends on:
ii  libc6   2.24-11+deb9u1
ii  libcairo2   1.14.8-1
ii  libgdk-pixbuf2.0-0  2.36.5-2+deb9u1
ii  libgladeui-2-6  3.20.2-1
ii  libglib2.0-02.50.3-2
ii  libgtk-3-0  3.22.11-1
ii  libpango-1.0-0  1.40.5-1

Versions of packages glade recommends:
ii  devhelp   3.22.0-1+b1
ii  libgtk-3-dev  3.22.11-1

glade suggests no packages.

-- no debconf information

Bug#885251: ITP: golang-github-rs-zerolog -- Zero Allocation JSON Logger

[Alexandre Viau]

Package: wnpp
Severity: wishlist
Owner: Alexandre Viau 

* Package name: golang-github-rs-zerolog
  Version : 1.3.0+git20171214.c2fc1c6-1
  Upstream Author : Olivier Poitrey 
* URL : https://github.com/rs/zerolog
* License : Expat
  Programming Lang: Go
  Description : Zero Allocation JSON Logger

-- 
Alexandre Viau
av...@debian.org



signature.asc
Description: OpenPGP digital signature

Bug#885248: syslog-ng: FTBFS on hurd-i386: typos in get_path_max

[Aaron M. Ucko]

Source: syslog-ng
Version: 3.13.2-1
Severity: important
Tags: upstream
Justification: fails to build from source (but built successfully in the past)

Builds of syslog-ng for hurd-i386 (admittedly not a release
architecture) have been failing lately:

  /<>/debian/build-tree/../../modules/affile/directory-monitor.c: 
In function 'get_path_max':
  
/<>/debian/build-tree/../../modules/affile/directory-monitor.c:87:11:
 error: 'pathmax' undeclared (first use in this function); did you mean 
'path_max'?
 pathmax++;
 ^~~
 path_max
  
/<>/debian/build-tree/../../modules/affile/directory-monitor.c:87:11:
 note: each undeclared identifier is reported only once for each function it 
appears in
  
/<>/debian/build-tree/../../modules/affile/directory-monitor.c:126:1:
 error: invalid storage class for function '_get_real_path'
  [...]

It's great that directory-monitor.c already attempts to accommodate
systems like the Hurd with no fixed PATH_MAX, but there are a couple
of typos in the relevant code.  Please try removing the unbalanced
(and unneeded) { on line 65 and fixing the spelling of path_max on
line 87.

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

Bug#885247: ITP: golang-github-zenazn-goji -- Goji is a minimalistic web framework for Golang that's high in antioxidants

[Alexandre Viau]

Package: wnpp
Severity: wishlist
Owner: Alexandre Viau 

* Package name: golang-github-zenazn-goji
  Version : 1.0+git20170812.c05078c-1
  Upstream Author : Carl Jackson
* URL : https://github.com/zenazn/goji
* License : Expat
  Programming Lang: Go
  Description : Goji is a minimalistic web framework for Golang
that's high in antioxidants.

this is needed for influxdb

-- 
Alexandre Viau
av...@debian.org



signature.asc
Description: OpenPGP digital signature

Bug#885246: peewee: FTBFS on hurd-i386: sqlite3.OperationalError: database is locked

[Aaron M. Ucko]

Source: peewee
Version: 2.10.2+dfsg-2
Severity: important
Tags: upstream
Justification: fails to build from source
User: debian-h...@lists.debian.org
Usertags: hurd-i386

The build of peewee for hurd-i386 (admittedly not a release
architecture) failed with test suite errors boiling down to

  sqlite3.OperationalError: database is locked

as detailed at
https://buildd.debian.org/status/fetch.php?pkg=peewee=hurd-i386=2.10.2%2Bdfsg-2=1513960535=0.

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

Bug#885245: linux: FTBFS on powerpcspe: sstep.c: ptesync unrecognized

[Aaron M. Ucko]

Source: linux
Version: 4.14.7-1
Severity: important
Tags: upstream
Justification: fails to build from source (but built successfully in the past)
User: debian-powe...@lists.debian.org
Usertags: powerpcspe

Builds of linux for powerpcspe (admittedly not a release architecture)
have been failing lately:

  {standard input}: Assembler messages:
  {standard input}:5854: Error: unrecognized opcode: `ptesync'
  /<>/scripts/Makefile.build:319: recipe for target 
'arch/powerpc/lib/sstep.o' failed
  make[6]: *** [arch/powerpc/lib/sstep.o] Error 1

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

Bug#874090: debian-policy: Clarify wording of some passages

[Russ Allbery]

Control: tags -1 = pending

Ben Finney  writes:

> I have made some minor clarifying changes while working on another bug
> report.

> These changes do not have any substantive effect on the intended meaning
> of the passages, only to clarity of expression.

Thanks, these all look good to me.  Applied.  And many thanks for the
clear, separated patches!  That made review very easy.

-- 
Russ Allbery (r...@debian.org)   

Bug#885244: ITP: golang-github-goji-param -- Rack / jQuery style parameter parsing for Go

[Alexandre Viau]

Package: wnpp
Severity: wishlist
Owner: Alexandre Viau 

* Package name: golang-github-goji-param
  Version : 0.0~git20160927.d7f49fd-1
  Upstream Author : Goji
* URL : https://github.com/goji/param
* License : Expat
  Programming Lang: Go
  Description : Rack / jQuery style parameter parsing for Go

 Param GoDoc (https://godoc.org/github.com/goji/param) param deserializes
 parameter values into a given struct using magical reflection ponies.
 .
 Inspired by gorilla/schema, but uses Rails/jQuery style param encoding
 instead of their weird dotted syntax. In particular, this package was
 written with the intent of parsing the output of jQuery.param.

-- 
Alexandre Viau
av...@debian.org



signature.asc
Description: OpenPGP digital signature

Bug#885243: libgaminggear: FTBFS on non-Linux: Neither uhid nor uinput was found

[Aaron M. Ucko]

Source: libgaminggear
Version: 0.15.1-2
Severity: important
Justification: fails to build from source
User: debian-h...@lists.debian.org
Usertags: hurd-i386

Builds of libgaminggear for (non-release) non-Linux architectures
(hurd-i386 so far, presumably also kfreebsd-*) have been failing:

  CMake Error at CMakeLists.txt:39 (MESSAGE):
Neither uhid nor uinput was found

If support for these Linux APIs is essential, please formally restrict
the package's architecture to linux-any accordingly, so that other
architectures' autobuilders don't bother trying to cover it.

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

Bug#885242: libnitrokey: FTBFS (32-bit): symbols not as expected

[Aaron M. Ucko]

Source: libnitrokey
Version: 3.1-1
Severity: important
Justification: fails to build from source

Builds of libnitrokey for 32-bit architectures such as i386 have been
failing because the library's symbols differ somewhat from the
expectations in libnitrokey3.symbols, as detailed at

https://buildd.debian.org/status/logs.php?pkg=libnitrokey=3.1-1

Could you please take a look and account for this variation (bearing
in mind that the details may turn out to be architecture-dependent)?

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

Bug#885240: libmsnumpress: FTBFS: dot and qhelpgenerator not found

[Aaron M. Ucko]

Source: libmsnumpress
Version: 1.0.0-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Builds of libmsnumpress in minimal environments (as on the
autobuilders) have been failing:

  mkdir -p debian/build && doxygen debian/Doxyfile
  warning: the dot tool could not be found at /usr/bin/dot
  [...]
  sh: 1: dot: not found
  [...]
  error: problems opening map file 
/<>/debian/build/doxygen/html/MSNumpress_8cpp__incl.map for 
inclusion in the docs!
  If you installed Graphviz/dot after a previous failing run, 
  try deleting the output directory and rerun doxygen.
  [...]
  sh: 1: /usr/bin/qhelpgenerator: not found
  error: failed to run qhelpgenerator on index.qhp
  [...]
  find debian/build/doxygen/html -name "*.md5" | xargs rm
  find debian/build/doxygen/html -name "*.map" | xargs rm
  rm: missing operand
  Try 'rm --help' for more information.
  debian/rules:30: recipe for target 'override_dh_auto_build' failed
  make[1]: *** [override_dh_auto_build] Error 123
  make[1]: Leaving directory '/<>'
  debian/rules:12: recipe for target 'build-arch' failed
  make: *** [build-arch] Error 2

Given that the docs have their own binary package anyway, I'd suggest
splitting override_dh_auto_build into -arch and -indep variants and
splitting out a Build-Depends Indep for doxygen, libjs-jquery, and
anything else you need when building documentation but left out
earlier.

Thanks!

FTR, I'm filing this bug as a regression because it would affect any
needed binary-only rebuilds for amd64.

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

Bug#885241: glade: Gtypes mangled when packed in pointers in glade-base-editor

[William Panlener]

Package: glade
Version: 3.20.2-1
Severity: normal
Tags: upstream patch

Dear Maintainer,

   When attempting to add a cell renderer to a GTKTreeViewColumn, it was
discovered
   that this feature is broken in glade.

   To reproduce: Add a GTKTreeView to a GTKWindow in glade.  Right click the
   GTKTreeView and select "Edit" in the popup window. In the Hierarchy pane,
click
   the + (plus) icon to add a new GTKTreeViewColumn. Right click the new column
and
   choose "Add child Text" from the popup window.

   It is expected that a GTKCellRendererText object would appear as a child of
the
   GTKTreeViewColumn, but instead, nothing happens. Other buggy behavior can be
   seen in this same Hierarchy pane such as occasional segfaults when removing
   columns.

   After debugging, it seems that this behavior and probable buggy behavior
with
   other GTK+ plugins using the glade-base-editor can be attributed to mangling
of
   GType values that occurs when packing these values into gints. GType is an
8-byte
   unsigned value while gint is a signed 4 byte value (at least on amd64).

   These patches were tested on a backport of glade from unstable (3.20.2-1) to
stretch
   with libglib-dev and debhelper build-dep versions relaxed to meet those in
stretch,
   the behavior bug is also present in the stable package (3.20.0-2) and
appears to be
   present upstream (untested but apparent in source and unmentioned in
Changelog). The
   report has not been forwarded upstream.

   The patch consists of a macro wrapper to pack GTypes in a larger integer
type and a
   test to preempt regression. Ideally, most of this would be provided by glib.



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

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

Versions of packages glade depends on:
ii  libc6   2.24-11+deb9u1
ii  libcairo2   1.14.8-1
ii  libgdk-pixbuf2.0-0  2.36.5-2+deb9u1
ii  libgladeui-2-6  3.20.2-1
ii  libglib2.0-02.50.3-2
ii  libgtk-3-0  3.22.11-1
ii  libpango-1.0-0  1.40.5-1

Versions of packages glade recommends:
ii  devhelp   3.22.0-1+b1
ii  libgtk-3-dev  3.22.11-1

glade suggests no packages.

-- no debconf information

*** /home/william/Desktop/glade-bug/Avoid_data_loss_when_packing_gtype.patch
Description: Avoid data loss when packing GType
 Gtypes are unsigned longs but were packed into a
 signed int causing data loss and undesirable
 behavior in the tree view editor and likely
 all other gtk plugins utilizing glade-base-editor.
 .
 glade (3.20.0-2) stable; urgency=medium
 .
Author: William Panlener 
Bug-Debian: https://bugs.debian.org/837832

---

Bug-Debian: https://bugs.debian.org/
Forwarded: 
Last-Update: 2017-12-25

--- glade-3.20.0.orig/gladeui/glade-base-editor.c
+++ glade-3.20.0/gladeui/glade-base-editor.c
@@ -784,7 +784,7 @@ glade_base_editor_add_item_activate (Gtk
  GladeBaseEditor *e)
 {
   GObject *item = G_OBJECT (menuitem);
-  GType type = GPOINTER_TO_INT (g_object_get_data (item, "object_type"));
+  GType type = GPOINTER_TO_TYPE (g_object_get_data (item, "object_type"));
   GladeBaseEditorAddMode add_mode =
   GPOINTER_TO_INT (g_object_get_data (item, "object_add_mode"));

@@ -825,7 +825,7 @@ glade_base_editor_popup (GladeBaseEditor
 gtk_widget_show (item);

 g_object_set_data (G_OBJECT (item), "object_type",
-   GINT_TO_POINTER (iter_type));
+   GTYPE_TO_POINTER (iter_type));

 g_object_set_data (G_OBJECT (item), "object_add_mode",
GINT_TO_POINTER (ADD_SIBLING));
@@ -857,7 +857,7 @@ glade_base_editor_popup (GladeBaseEditor
 gtk_widget_show (item);

 g_object_set_data (G_OBJECT (item), "object_type",
-   GINT_TO_POINTER (iter_type));
+   GTYPE_TO_POINTER (iter_type));

 g_object_set_data (G_OBJECT (item), "object_add_mode",
GINT_TO_POINTER (ADD_CHILD));
--- glade-3.20.0.orig/gladeui/glade-base-editor.h
+++ glade-3.20.0/gladeui/glade-base-editor.h
@@ -34,6 +34,9 @@ G_BEGIN_DECLS
 #define GLADE_IS_BASE_EDITOR_CLASS(k)  (G_TYPE_CHECK_CLASS_TYPE ((k),
GLADE_TYPE_BASE_EDITOR))
 #define GLADE_BASE_EDITOR_GET_CLASS(o) (G_TYPE_INSTANCE_GET_CLASS ((o),
GLADE_TYPE_BASE_EDITOR, GladeBaseEditorClass))

+#define GTYPE_TO_POINTER(x) GSIZE_TO_POINTER(x)
+#define GPOINTER_TO_TYPE(x) GPOINTER_TO_SIZE(x)
+
 typedef struct _GladeBaseEditorGladeBaseEditor;
 typedef struct _GladeBaseEditorPrivate GladeBaseEditorPrivate;
 typedef struct _GladeBaseEditorClass   GladeBaseEditorClass;
--- glade-3.20.0.orig/tests/Makefile.am
+++ 

Bug#753456: lintian: false positive: privacy-breach-donation: pnp4nagios-web

[Paul Wise]

Control: tags -1 + wontfix
Control: close -1

On Sun, 2017-12-24 at 20:19 +, Chris Lamb wrote:

> True. Unfortunately from a quick look it's going to be overly fragile to
> weaken the Flattr check to simply check for the inclusion of the external
> Javascript; the magic "flattr" string in the "rel" HTML attributes surely
> telegraphs enough intention to include the script.
> 
> I also note that pnp4nagios-web only exists in wheezy these days. :)

Fair enough, lets close this request then.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#873456: debian-policy: missing anchor: document-index

[Russ Allbery]

Paul Wise  writes:

> There are several links that point to the document-index anchor, but it
> is not available in the document. This is especially annoying for users
> of text-based browsers because it means that there is no easy way to
> get to the Table of Contents, which used to be at the top of index.html

> $ grep -ri document-index /usr/share/doc/debian-policy/
> /usr/share/doc/debian-policy/policy.html/index.html: class="nav-item nav-item-0">Debian Policy 
> Manual v4.1.0.0  
> /usr/share/doc/debian-policy/policy.html/index.html:   href="index.html#document-index">Table Of Contents
> /usr/share/doc/debian-policy/policy.html/index.html: class="nav-item nav-item-0">Debian Policy 
> Manual v4.1.0.0  

This appears to be more breakage in Sphinx singlehtml output.  Everything
looks correct in the multi-page HTML output.

-- 
Russ Allbery (r...@debian.org)   

Bug#885233: libunwind8: undefined symbols: ptrace.so needs -llzma, {ptrace,coredump}.so needs -lunwind

[Paul Wise]

Package: libunwind8
Version: 1.2.1-5
Severity: minor
User: debian...@lists.debian.org
Usertags: undefined-symbol adequate

libunwind-coredump needs to link with -lunwind and libunwind-ptrace
needs to link with -lunwind -llzma, see the output of adequate and
symtree below. I detected this on amd64 but the Debian build log
scanner also detected dpkg-buildpackage complaining about it on most
architectures, see the w3m/getbuildlog output below.

I filed this bug at severity minor since the required symbols are
probably always available because programs using the ptrace/coredump
unwind libs probably always link against the main unwind lib.

This bug report brought to you by adequate:

http://bonedaddy.net/pabs3/log/2013/02/23/inadequate-software/

$ adequate libunwind8
libunwind8: undefined-symbol 
/usr/lib/x86_64-linux-gnu/libunwind-coredump.so.0.0.0 => _Ux86_64_get_elf_image
libunwind8: undefined-symbol 
/usr/lib/x86_64-linux-gnu/libunwind-coredump.so.0.0.0 => 
_Ux86_64_dwarf_find_unwind_table
libunwind8: undefined-symbol 
/usr/lib/x86_64-linux-gnu/libunwind-coredump.so.0.0.0 => 
_Ux86_64_dwarf_search_unwind_table
libunwind8: undefined-symbol 
/usr/lib/x86_64-linux-gnu/libunwind-ptrace.so.0.0.0 => lzma_stream_buffer_decode
libunwind8: undefined-symbol 
/usr/lib/x86_64-linux-gnu/libunwind-ptrace.so.0.0.0 => _Ux86_64_get_elf_image
libunwind8: undefined-symbol 
/usr/lib/x86_64-linux-gnu/libunwind-ptrace.so.0.0.0 => 
lzma_index_uncompressed_size
libunwind8: undefined-symbol 
/usr/lib/x86_64-linux-gnu/libunwind-ptrace.so.0.0.0 => 
_Ux86_64_dwarf_find_unwind_table
libunwind8: undefined-symbol 
/usr/lib/x86_64-linux-gnu/libunwind-ptrace.so.0.0.0 => 
_Ux86_64_dwarf_search_unwind_table
libunwind8: undefined-symbol 
/usr/lib/x86_64-linux-gnu/libunwind-ptrace.so.0.0.0 => lzma_index_end
libunwind8: undefined-symbol 
/usr/lib/x86_64-linux-gnu/libunwind-ptrace.so.0.0.0 => lzma_index_buffer_decode
libunwind8: undefined-symbol 
/usr/lib/x86_64-linux-gnu/libunwind-ptrace.so.0.0.0 => lzma_stream_footer_decode
libunwind8: undefined-symbol 
/usr/lib/x86_64-linux-gnu/libunwind-ptrace.so.0.0.0 => lzma_index_size
$ man adequate | grep -A4  undefined-symbol
   undefined-symbol
   The symbol has not been found in the libraries linked with the 
binary.  Either the binary either needs to be linked with an additional shared 
library, or the dependency
   on the shared library package that provides this symbol is too weak.

   References: Debian Policy §3.5, §8.6, §10.2.
$ dpkg -L libunwind8 | grep /usr/lib/
/usr/lib/x86_64-linux-gnu
/usr/lib/x86_64-linux-gnu/libunwind-coredump.so.0.0.0
/usr/lib/x86_64-linux-gnu/libunwind-ptrace.so.0.0.0
/usr/lib/x86_64-linux-gnu/libunwind-x86_64.so.8.0.1
/usr/lib/x86_64-linux-gnu/libunwind.so.8.0.1
/usr/lib/x86_64-linux-gnu/libunwind-coredump.so.0
/usr/lib/x86_64-linux-gnu/libunwind-ptrace.so.0
/usr/lib/x86_64-linux-gnu/libunwind-x86_64.so.8
/usr/lib/x86_64-linux-gnu/libunwind.so.8
$ lddtree /usr/lib/x86_64-linux-gnu/libunwind-ptrace.so.0.0.0
libunwind-ptrace.so.0.0.0 => 
/usr/lib/x86_64-linux-gnu/libunwind-ptrace.so.0.0.0 (interpreter => none)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6
ld-linux-x86-64.so.2 => /lib/x86_64-linux-gnu/ld-linux-x86-64.so.2
$ symtree /usr/lib/x86_64-linux-gnu/libunwind-ptrace.so.0.0.0
/usr/lib/x86_64-linux-gnu/libunwind-ptrace.so.0.0.0
libc.so.6 => 
strncpy,mmap,strlen,__errno_location,malloc,munmap,ptrace,__cxa_finalize,free
WEAK => _ITM_deregisterTMCloneTable,__gmon_start__,_ITM_registerTMCloneTable
UNRESOLVED => 
lzma_stream_buffer_decode,_Ux86_64_get_elf_image,lzma_index_uncompressed_size,_Ux86_64_dwarf_find_unwind_table,_Ux86_64_dwarf_search_unwind_table,lzma_index_end,lzma_index_buffer_decode,lzma_stream_footer_decode,lzma_index_size
$ lddtree /usr/lib/x86_64-linux-gnu/libunwind-coredump.so.0.0.0 
libunwind-coredump.so.0.0.0 => 
/usr/lib/x86_64-linux-gnu/libunwind-coredump.so.0.0.0 (interpreter => none)
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2
ld-linux-x86-64.so.2 => /lib/x86_64-linux-gnu/ld-linux-x86-64.so.2
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6
$ symtree /usr/lib/x86_64-linux-gnu/libunwind-coredump.so.0.0.0
/usr/lib/x86_64-linux-gnu/libunwind-coredump.so.0.0.0
liblzma.so.5 => 
lzma_stream_buffer_decode,lzma_stream_footer_decode,lzma_index_end,lzma_index_uncompressed_size,lzma_index_size,lzma_index_buffer_decode
libc.so.6 => 
__strdup,strncpy,mmap,calloc,strlen,read,lseek,malloc,munmap,__fxstat,close,open,write,free
UNRESOLVED => 
_Ux86_64_get_elf_image,_Ux86_64_dwarf_find_unwind_table,_Ux86_64_dwarf_search_unwind_table
$ lddtree /usr/lib/x86_64-linux-gnu/libunwind-x86_64.so.8
libunwind-x86_64.so.8 => /usr/lib/x86_64-linux-gnu/libunwind-x86_64.so.8 
(interpreter => none)
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5
libdl.so.2 => 

Bug#885232: ITP: golang-gopkg-inconshreveable-log15.v2 -- Structured, composable logging for Go

[Alexandre Viau]

Package: wnpp
Severity: wishlist
Owner: Alexandre Viau 

* Package name: golang-gopkg-inconshreveable-log15.v2
  Version : 2.13-1
  Upstream Author : Alan Shreve
* URL : https://github.com/inconshreveable/log15
* License : Apache-2.0
  Programming Lang: Go
  Description : Structured, composable logging for Go

This is needed for influxdb

-- 
Alexandre Viau
av...@debian.org



signature.asc
Description: OpenPGP digital signature

Bug#874095: copyright-format: Use the “synopsis” term established in the definition

[Russ Allbery]

Control: tags -1 pending

Ben Finney  writes:

> The term “synopsis” is established in the definition of “Formatted
> Text”. This attached patch uses that term more consistently in the
> document.

Thanks, looks good to me.  Applied.

-- 
Russ Allbery (r...@debian.org)   

Bug#883851: kodi: Crash Loop when inserting Audio CD

[Bálint Réczey]

Control: tags -1 confirmed

Hi Sebastian,

2017-12-08 11:16 GMT+01:00 Sebastian Bachmann :
> Package: kodi
> Version: 2:17.3+dfsg1-5+b3
> Severity: important
>
> Dear Maintainer,
>
> I noticed today that inserting any Audio CD (I tried a few) results in a crash
> loop. Kodi will constantly crash and restart.
>
> I collected the outputs in /var/log/daemon.log and the kodi crashlog.
>
> If you need any more information, I would be glad to help!

I hoped the crash would go away with recompiling with latest libcdio,
but i can still reproduce it with kodi 17.6. :-(
This needs more investigation.

Cheers,
Balint

Bug#880992: debian-policy should not recommend running editor using absolute path

[Russ Allbery]

Control: tags -1 patch

Jonathan Nieder  writes:

> If read strictly, this says that I must use "/usr/bin/editor" instead of
> invoking "editor" from the $PATH.  (I'm not sure I agree with that
> interpretation, but it came up in https://bugs.debian.org/682347.)
> Running "editor" from the $PATH instead of using that full path should
> be perfectly acceptable and IMHO is a better behavior, since it allows
> the user to put a custom editor in /usr/local/bin or $HOME/bin.

> Could this say something like

>   not set, the commands "editor" and "pager" should be used,
>   respectively. These commands can be invoked explicitly (e.g.
>   as /usr/bin/editor), or through a $PATH search (e.g. as
>   editor).

> ?

This wording seems fine to me.  Seconded.  (I volunteer to turn this into
a Git change if it gets enough seconds.)

-- 
Russ Allbery (r...@debian.org)