Bug#834396: Workaround with CPU binding

[Tian Bo]

I ran into the same crash problem when I use 'reread' command to update my
plot. As pointed out in the above post, using single thread could work
around the bug. However, rebuilding gnuplot may not be  an option for most
user.

My workaround approach is to run gnuplot in a single CPU core by means of
the command 'taskset' (on linux). For exmple:

taskset -c 0 gnuplot ...

This command runs gnuplot on CPU 0, so that it is effectively a
single-thread process and the problem is avoided.

Bug#886417: linux-source-4.9: Kernel sources do not compile

[Robert Senger]

Package: linux-source-4.9
Version: 4.9.65-3+deb9u2
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Dear Maintainer,

compilation of Kernel sources 4.9.65-3+deb9u2 fails:

[snip]
  CC  arch/x86/mm/gup.o
  CC  arch/x86/mm/setup_nx.o
  CC  arch/x86/mm/tlb.o
arch/x86/mm/tlb.c: In function ‘switch_mm_irqs_off’:
arch/x86/mm/tlb.c:160:3: error: implicit declaration of function
‘load_new_mm_cr3’ [-Werror=implicit-function-declaration]
   load_new_mm_cr3(next->pgd);
   ^~~
cc1: some warnings being treated as errors
scripts/Makefile.build:298: die Regel für Ziel „arch/x86/mm/tlb.o“ scheiterte
make[3]: *** [arch/x86/mm/tlb.o] Fehler 1
scripts/Makefile.build:549: die Regel für Ziel „arch/x86/mm“ scheiterte
make[2]: *** [arch/x86/mm] Fehler 2
Makefile:995: die Regel für Ziel „arch/x86“ scheiterte
make[1]: *** [arch/x86] Fehler 2
make[1]: Verzeichnis „/usr/src/linux-4.9.65“ wird verlassen
debian/ruleset/targets/common.mk:295: die Regel für Ziel
„debian/stamp/build/kernel“ scheiterte
make: *** [debian/stamp/build/kernel] Fehler 2




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

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

Versions of packages linux-source-4.9 depends on:
ii  binutils  2.28-5
ii  xz-utils  5.2.2-1.2+b1

Versions of packages linux-source-4.9 recommends:
ii  bc1.06.95-9+b3
ii  gcc   4:6.3.0-4
ii  libc6-dev [libc-dev]  2.24-11+deb9u1
ii  make  4.1-9.1

Versions of packages linux-source-4.9 suggests:
pn  libncurses-dev | ncurses-dev  
pn  libqt4-dev
ii  pkg-config0.29-4+b1

Bug#886418: ITP: kwant -- Python package for numerical quantum transport calculations

[Christoph Groth]

Package: wnpp
Severity: wishlist
Owner: Christoph Groth 

* Package name: kwant
  Version : 1.3.2
  Upstream Author : Kwant authors 
* URL : http://www.kwant-project.org/
* License : BSD
  Programming Lang: Python, Cython
  Description : Python package for numerical quantum transport

 Kwant is a Python package for numerical quantum transport
 calculations. It exposes the natural concepts of the theory of quantum
 transport (lattices, symmetries, electrodes, orbital/spin/electron-hole
 degrees of freedom) in a simple and transparent way. Kwant offers direct
 support for calculations of transport properties (conductance, noise,
 scattering matrix), dispersion relations, modes, wave functions, various
 Green’s functions, and out-of-equilibrium local quantities. Other
 computations involving tight-binding Hamiltonians can be implemented
 easily.

Kwant is a scientific library that is popular with condensed matter
physicists.  Since it became public in 2013, Kwant has been used by
researchers around the world in numerous projects that lead to over 180
scientific articles.  In 2017 alone the number of such publications was
80. [1]

I'm one of the main developers of Kwant and have been maintaining
unofficial Debian and Ubuntu packages for it since 2013.  We're
committed to maintain both Kwant and its Debian package for years to
come.  Since I haven't been active in Debian so far, I need a sponsor
for this package.

Kwant depends on tinyarray [2], a Python extension module written in C++
that implements a subset of NumPy that is optimized for very small
arrays.  Tinyarray is fully independent of Kwant, but has seen little use 
outside of Kwant.  Shall I file an ITP for tinyarray as well?

[1] 
http://adsabs.harvard.edu/cgi-bin/nph-ref_history?refs=CITATIONS=2014NJPh...16f3065G
[2] https://gitlab.kwant-project.org/kwant/tinyarray

Bug#886401: evince: Evince does not start: Error in `evince': double free or corruption (fasttop)

[Jason Crain]

Control: tags -1 + moreinfo

On Fri, Jan 05, 2018 at 11:48:21AM +, Geoffrey Ferrari wrote:
>* What led up to the situation?
> Trying to run evince from command line or from gnome desktop, without or
> without a pdf file to view.
> 
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
> Tried executing "evince" from command line with no pdf file specified.
>* What was the outcome of this action?
> 
> The following error message is reported:
> *** Error in `evince': double free or corruption (fasttop): 0x55884b31a380
> ***

Can you provide a backtrace with debug symbols?  You'll need to install
at least evince-dbgsym, libevdocument3-4-dbgsym, libevview3-3-dbgsym,
libglib2.0-0-dbgsym, libgtk-3-0-dbgsym, libpango-1.0-0-dbgsym,
libpangoft2-1.0-0-dbgsym, libpangocairo-1.0-0-dbgsym,
libfontconfig1-dbgsym, and libexpat1-dbgsym.

https://wiki.debian.org/HowToGetABacktrace#Installing_the_debugging_symbols
describes how to enable the repo for the dbgsym packages.

Bug#877866: skrooge: crashes when saving to a new file

[Thierry Jeanmougin]

Package: skrooge
Version: 2.7.0-1
Followup-For: Bug #877866

Dear Maintainer,

same issue.
Before the segmentation fault, I get this warning:
Invalid URL: QUrl ("myfile.skg"), myfile being the file name to be saved

The only workaround I have found is to use a Jessie VM to create new
files. Not very convenient.


-- System Information:
Debian Release: 9.3
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'unstable')
Architecture: amd64 (x86_64)

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

Versions of packages skrooge depends on:
ii  kinit5.28.0-1
ii  kio  5.28.0-2
ii  libc62.24-11+deb9u1
ii  libgcc1  1:6.3.0-18
ii  libgrantlee-templates5   5.1.0-2
ii  libkf5archive5   5.28.0-2
ii  libkf5completion55.28.0-1
ii  libkf5configcore55.28.0-2
ii  libkf5configgui5 5.28.0-2
ii  libkf5configwidgets5 5.28.0-2
ii  libkf5coreaddons55.28.0-2
ii  libkf5dbusaddons55.28.0-1
ii  libkf5i18n5  5.28.0-2
ii  libkf5iconthemes55.28.0-2
ii  libkf5itemviews5 5.28.0-1
ii  libkf5kiocore5   5.28.0-2
ii  libkf5kiofilewidgets55.28.0-2
ii  libkf5newstuff5  5.28.0-1
ii  libkf5notifications5 5.28.0-1
ii  libkf5notifyconfig5  5.28.0-1
ii  libkf5parts5 5.28.0-1
ii  libkf5runner55.28.0-1
ii  libkf5service-bin5.28.0-1
ii  libkf5service5   5.28.0-1
ii  libkf5textwidgets5   5.28.0-1
ii  libkf5wallet-bin 5.28.0-3
ii  libkf5wallet55.28.0-3
ii  libkf5widgetsaddons5 5.28.0-3
ii  libkf5xmlgui55.28.0-1
ii  libofx6  1:0.9.10-2+deb9u1
ii  libqca-qt5-2 2.1.1-4+b2
ii  libqca-qt5-2-plugins 2.1.1-4+b2
ii  libqt5concurrent55.7.1+dfsg-3+b1
ii  libqt5core5a [qtbase-abi-5-7-1]  5.7.1+dfsg-3+b1
ii  libqt5dbus5  5.7.1+dfsg-3+b1
ii  libqt5gui5   5.7.1+dfsg-3+b1
ii  libqt5printsupport5  5.7.1+dfsg-3+b1
ii  libqt5qml5   5.7.1-2+b2
ii  libqt5quick5 5.7.1-2+b2
ii  libqt5quickwidgets5  5.7.1-2+b2
ii  libqt5script55.7.1~20161021+dfsg-2
ii  libqt5sql5   5.7.1+dfsg-3+b1
ii  libqt5sql5-sqlite5.7.1+dfsg-3+b1
ii  libqt5svg5   5.7.1~20161021-2+b2
ii  libqt5webkit55.7.1+dfsg-1
ii  libqt5widgets5   5.7.1+dfsg-3+b1
ii  libqt5xml5   5.7.1+dfsg-3+b1
ii  libsqlcipher03.2.0-2
ii  libstdc++6   6.3.0-18
ii  skrooge-common   2.7.0-1

Versions of packages skrooge recommends:
ii  poppler-utils  0.48.0-2

skrooge suggests no packages.

-- no debconf information

Bug#874305: RFS: mitlm/0.4.2-1 -- MIT Language Modeling toolkit

[Giulio Paci]

X-Debbugs-CC: jw...@debian.org
Control: tags -1 - moreinfo

Hi Adam and Tobias,
  thank you for having a look at this.

On 15/12/2017 14:09, Adam Borowski wrote:
> On Mon, Sep 04, 2017 at 10:49:36PM +0200, Giulio Paci wrote:
>> Dear Jakub,
>>
>>   I am looking for a sponsor for an updated version of my package "mitlm"
> 
> Apparently you forgot to CC jwilk; this RFS went only to the mentors
> mailinglist -- yet, upon seeing the first line, we assumed you want your
> usual sponsor.

You are right. I am CCing him now.

>> * Package name: mitlm
>>   Version : 0.4.2
> 
> I'm afraid it fails to build:
> /<>/./configure: line 20515: AX_CXX_HEADER_TR1_UNORDERED_MAP: 
> command not found
> /<>/./configure: line 20516: syntax error near unexpected token 
> `noext,'
> /<>/./configure: line 20516: `AX_CXX_COMPILE_STDCXX_11(noext, 
> optional)'

I added the autoconf-archive missing dependency.

On 04/01/2018 11:58, Tobias Frost wrote:
> Other notes: (Note that I did NOT a complete review)
> - Are you sure you want it uploaded to experimental? Why?

Indeed I am not sure, and actually prefer to have mitlm in unstable.

We decided to upload it to experimental, because of many uncertainties about 
both upstream development and about the package development (I was new to 
packaging when we
uploaded there).

As my long term goal is to have typical "development" packages for speech 
recognition and speech synthesis in Debian, I would really like to see mitlm in 
unstable.

> - d/compat could be bumped.

Done.

> - (S-V has increased in the meantime too, when over it you might want
> to update that to the latest)

Done.

> - maybe consider switching to debhelper (and dh_autoreconf). I'm pretty
> sure that will simplify d/rules a lot. (This would be whishlist entry
> of mine, not required at all)

Considered and done. :-)

> Please fix the FTBFS (and if you want the stuff above), then remove the
> moreinfo when ready!

Done by adding the missing dependency.

Bug#886416: libnih: uninstallable, and FTBFS when rebuilt: FAIL test_parse (unexpected line numbering)

[Simon McVittie]

Source: libnih
Version: 1.0.3-9
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Affects: systemd-shim

libnih was made uninstallable by the glibc 2.26 transition, because it
uses internal glibc symbols. Normally this would be handled by a simple
rebuild. However, the recent binNMU of libnih against glibc 2.26 failed:

> Testing parse_xml()
> ...
> BAD: wrong content in file 0x13be5e730 (output), expected 'test:foo:2:0: 
> Invalid object path in  name attribute
> ' got 'test:foo:1:36: Invalid object path in  name attribute
> '
>at tests/test_parse.c:7954 (test_parse_xml).
> FAIL test_parse (exit status: 134)

I don't know whether the test failure is triggered by glibc 2.26, or by
something else that changed since November.

This is particularly nasty because the missing binNMU makes libnih
(and hence systemd-shim) uninstallable; and until #883569 and #883573
are resolved, that's going to cause problems on the buildds whenever
a chain of (build-)dependencies pulls in libpam-systemd, because apt
apparently commits to installing systemd-shim and is not able to roll
back far enough to consider installing systemd-sysv instead.

smcv

Bug#886415: Unattended-upgrades not detecting Linux kernel security update by default

[Sam Kuper]

Package: unattended-upgrades
Version: 0.93.1+nmu1

(N.B. in the below, I have replaced the domain of my VPS hosting
provider with ``, for privacy.)

My Debian 9.3 "Stretch" instance is showing a kernel update as being available:

# apt list --upgradable -a
Listing... Done
linux-image-amd64/stable 4.9+80+deb9u3 amd64 [upgradable from:
4.9+80+deb9u2]
linux-image-amd64/stable,now 4.9+80+deb9u2 amd64
[installed,upgradable to: 4.9+80+deb9u3]

I believe `4.9+80+deb9u3` is the same as `4.9.65-3+deb9u2`, a recent
kernel security update (intended to address
[CVE-2017-5754](https://security-tracker.debian.org/tracker/CVE-2017-5754),
aka 
[Meltdown](https://en.wikipedia.org/wiki/Meltdown_(security_vulnerability))).


## Default config fails to install kernel security update

The default contents of `Unattended-Upgrade::Origins-Pattern` in
`/etc/apt/apt.conf.d/50unattended-upgrades` is:

Unattended-Upgrade::Origins-Pattern {
"origin=Debian,codename=${distro_codename},label=Debian-Security";
};

With that configuration in place, the kernel security update fails to
be installed:

# unattended-upgrades -v -d
Initial blacklisted packages:
Initial whitelisted packages:
Starting unattended upgrades script
Allowed origins are:
['origin=Debian,codename=stretch,label=Debian-Security']
Checking: linux-image-amd64 ([.com' isTrusted:True>])
pkg 'firmware-linux-free' not in allowed origin
sanity check failed
pkgs that look like they should be upgraded:
Fetched 0 B in 0s (0 B/s)
fetch.run() result: 0
blacklist: []
whitelist: []
Packages that will be upgraded:
InstCount=0 DelCount=0 BrokenCount=0
Extracting content from
'/var/log/unattended-upgrades/unattended-upgrades-dpkg.log' since
'2018-01-05 13:11:22'
Sending mail to 'root'
mail returned: 0

This is against my expectations. I suspect most sysadmins would like
unattended-upgrades, with such an Origin-Pattern in place, to install
kernel security updates.

(If my expectations are somehow misguided, and the behaviour above is
expected by the maintainer of unattended-upgrades, I would be grateful
for an explanation of why that is the case. Alternatively, if a bug is
present but lies outside the unattended-upgrades package - for
instance, if the kernel update was improperly released via a
repository other than Debian-security - then please could you confirm
this, so that this bug report can be re-filed against the correct
package.)



## Modified config installs kernel security update

If I change `Unattended-Upgrade::Origins-Pattern` in
`/etc/apt/apt.conf.d/50unattended-upgrades` to read

Unattended-Upgrade::Origins-Pattern {
"origin=Debian,codename=${distro_codename},label=Debian";
"origin=Debian,codename=${distro_codename},label=Debian-Security";
};

then the security update is found and installed:

# unattended-upgrades -v -d
Initial blacklisted packages:
Initial whitelisted packages:
Starting unattended upgrades script
Allowed origins are:
['origin=Debian,codename=stretch,label=Debian',
'origin=Debian,codename=stretch,label=Debian-Security']
Checking: linux-image-amd64 ([.com' isTrusted:True>])
pkgs that look like they should be upgraded: linux-image-amd64
Fetched 0 B in 0s (0 B/s)
fetch.run() result: 0
http://mirror..com/debian/pool/main/f/firmware-free/firmware-linux-free_3.4_all.deb'
ID:0 ErrorText: ''>

check_conffile_prompt('/var/cache/apt/archives/firmware-linux-free_3.4_all.deb')
No conffiles in deb
'/var/cache/apt/archives/firmware-linux-free_3.4_all.deb' (There is no
member named 'conffiles')
http://mirror..com/debian/pool/main/n/numactl/libnuma1_2.0.11-2.1_amd64.deb'
ID:0 ErrorText: ''>

check_conffile_prompt('/var/cache/apt/archives/libnuma1_2.0.11-2.1_amd64.deb')
No conffiles in deb
'/var/cache/apt/archives/libnuma1_2.0.11-2.1_amd64.deb' (There is no
member named 'conffiles')
http://mirror..com/debian-security/pool/updates/main/l/linux/linux-image-4.9.0-5-amd64_4.9.65-3+deb9u2_amd64.deb'
ID:0 ErrorText: ''>

check_conffile_prompt('/var/cache/apt/archives/linux-image-4.9.0-5-amd64_4.9.65-3+deb9u2_amd64.deb')
No conffiles in deb
'/var/cache/apt/archives/linux-image-4.9.0-5-amd64_4.9.65-3+deb9u2_amd64.deb'
(There is no member named 'conffiles')
http://mirror..com/debian-security/pool/updates/main/l/linux-latest/linux-image-amd64_4.9+80+deb9u3_amd64.deb'
ID:0 ErrorText: ''>

check_conffile_prompt('/var/cache/apt/archives/linux-image-amd64_4.9+80+deb9u3_amd64.deb')
found pkg: linux-image-amd64
No conffiles in deb
'/var/cache/apt/archives/linux-image-amd64_4.9+80+deb9u3_amd64.deb'
(There is no member named 'conffiles')
http://mirror..com/debian/pool/main/i/irqbalance/irqbalance_1.1.0-2.3_amd64.deb'
ID:0 ErrorText: ''>

check_conffile_prompt('/var/cache/apt/archives/irqbalance_1.1.0-2.3_amd64.deb')
blacklist: []
whitelist: []

Bug#886414: wpasupplicant: please re-enable WNM support

[Reiner Herrmann]

Package: wpasupplicant
Version: 2:2.6-14
Severity: wishlist

Dear Maintainer,

in 2:2.6-14 you disabled CONFIG_WNM (because it "Hopefully really
closes: #833507"). For me this is a regression, as I was actually using
that feature, which enables support for 11v. I would really like to have
it re-enabled again. With 11v support clients in dense environments can
be more gracefully roamed to different BSSIDs.

Kind regards,
   Reiner


signature.asc
Description: PGP signature

Bug#883628: ITP: ioport -- direct access to I/O ports from the command line

[Tobias Frost]

On Fri, Jan 05, 2018 at 03:30:35PM +0100, Lubomir Rintel wrote:
> On Fri, 5 Jan 2018 12:16:10 +0100 Tobias Frost  wrote:
> > On Fri, Jan 05, 2018 at 11:44:55AM +0100, Lubomir Rintel wrote:
> > > On Fri, 05 Jan 2018 11:20:02 +0100 Lubomir Rintel 
> > > wrote:

> > > Should I be bumping the package version number for each udpate? Should
> > > I be adding a new changelog entry for each? Even if not
> > > uploaded/released?
> > 
> > You keep the Debian revision the same until it is sponsored.
> 
> That's what I initially meant to do, but mentors.debian.org won't let
> me upload a changed package with the same version number.
> 
> I suppose I perhaps should've used 1~x version numbers until the
> package passes a review, but it doesn't seem to be something I could do
> anything about anymore.
> 

IIRC you can just overwrite it with a new upload. Beside that,
you can manually delete old upload and then reupload as a last resort.

> > For the 1st upload, you do not add entries to the changelog as well, it
> > is just "Initial Packaging (Closes: #ITP-Bug-Number).
> > Subsequent uploads will go more into details then, listing every change
> > made to the packaging.
> 
> > I recommend to browse through the documents linked in "3. Make the package"
> > in https://mentors.debian.net/intro-maintainers. They will probably help you
> > a lot to get into the (difficult) topic of packaging.
> > I know its a lot to read, but it helps to know "where to look"; it is not
> > necessary that you memorize everything to the letter, but a rough idea where
> > something is explained will help. (and the knowledge will also come with
> > using it anyway)
> 
> Yeah, I'm familiar with it (the link, not necessarily the content).
> 
> Still, while probably a great reference, the documentation doesn't seem
> to be too good at providing best practices guidance (should the package
> be versioned in a VCS? Should I pick any hosting or is it typical to
> keep it on alioth/salsa? Should I always be relying on latest
> debhelper? Etc.). I suppose that builds up with experience.

Yes, experience is important. Otherwise you can also take a look at other
packages in the archive. 

> The updated package:
> 
> https://mentors.debian.net/debian/pool/main/i/ioport/ioport_1.2-4.dsc

You want Debian revision -1, not -4..
Sorry, have ask you again for another iteration...

> Thanks
> Lubo
> 

Bug#886222: ld.gold: internal error in get_got_page_offset, at ../../gold/mips.cc:6271

[Gianfranco Costamagna]

On Thu, 4 Jan 2018 14:30:08 + James Cowgill  wrote:
> Hi,
> 
> On 04/01/18 14:26, Gianfranco Costamagna wrote:
> > Hello,
> > 
> >> Is there a way for me to run your testcase without ghc-stage1 (which
> >> would require building ghc)?
> > 
> > I don't know, however I attached ghc-stage1 binaries to the report
> 
> The "ghc-stage1" you attached is a shell script which execs some other
> binary which you didn't attach.
> 

this is true, I hope you can get from my home in eller.debian.org :)

G.



signature.asc
Description: OpenPGP digital signature

Bug#886275: gourmet: Don't depend on python-poppler

[Jeremy Bicha]

Control: unmerge 879035
Control: severity 879035 important

On Wed, Jan 3, 2018 at 12:55 PM, Jeremy Bicha  wrote:
> Once the upload is accepted into Debian, we can lower the severity of
> https://bugs.debian.org/879035 to important.

I'm lowering the other bug's severity now even though the NMU to
disable poppler is still in the DELAYED queue.

Thanks,
Jeremy Bicha

Bug#872998: transition: PHP 7.0 to 7.1

[Ondřej Surý]

I have just uploaded next round of PHP upstream releases including 7.2.1 that 
clears all d/copyright issues that ftp-masters had.

I responded to the REJECT email, so hopefully this will speed up the process of 
accepting PHP 7.2 into the unstable.

Cheers,
-- 
Ondřej Surý 

On Thu, Jan 4, 2018, at 18:42, Emilio Pozuelo Monfort wrote:
> On 16/12/17 10:57, Emilio Pozuelo Monfort wrote:
> > On 08/12/17 19:55, Emilio Pozuelo Monfort wrote:
> >> On 05/12/17 17:23, Ondřej Surý wrote:
> >>> Hi Emilio,
> >>>
> >>> the php-defaults has been uploaded some time ago, and some extensions
> >>> have already been rebuild.
> >>
> >> Ah, I didn't know we were ready to schedule binNMUs.
> >>
> >>> However with PHP 7.2 release, it might make sense to take this one step
> >>> further and add PHP 7.2 as the target for the transition (after it
> >>> passes NEW queue).
> >>
> >> Ok, that makes sense. Let's wait for 7.2 to clear NEW and for php-defaults 
> >> to be
> >> updated, then.
> > 
> > 7.2 is out of NEW now. Let me know when php-defaults is updated and we're 
> > ready
> > for some binNMUs.
> 
> Any update on this?
> 
> Cheers,
> Emilio

Bug#869116: kcharselect: crashes when selecting some charsets

[Pino Toscano]

reassign 869116 src:kwidgetsaddons kwidgetsaddons/5.28.0-3
affects 869116 kcharselect
thanks

Hi,

On giovedì 20 luglio 2017 18:40:59 CET Guillaume Bertholon wrote:
> Package: kcharselect
> Version: 4:16.08.0-1+b1
> Severity: important
> 
> Dear Maintainer,
> 
> Each time I select one of the charsets "Latin Extended-B", "Latin Extended-D"
> or "Greek Extended" (non-exhaustive list), the application crashes with a
> Segmentation fault.
> 
> I have included the gdb backtrace after the SIGSEGV in case it could be 
> useful.

While the underlying crash seems to be in the Qt accessibility
integration with AtSpi [1], it was worked around in the character
selector widget (in the kwidgetsaddons framework) used by kcharselect.
Hence, reassigning to kwidgetsaddons, and closing soon.

[1] https://bugreports.qt.io/browse/QTBUG-58153

-- 
Pino Toscano

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

Bug#883628: ITP: ioport -- direct access to I/O ports from the command line

[Christian Seiler]

On 01/05/2018 03:30 PM, Lubomir Rintel wrote:

On Fri, 5 Jan 2018 12:16:10 +0100 Tobias Frost  wrote:

You keep the Debian revision the same until it is sponsored.


That's what I initially meant to do, but mentors.debian.org won't let
me upload a changed package with the same version number.


You can remove the old package on Mentors via the web interface and
then upload the package in that version again with different contents.

Note that in my experience reuploading an existing version to Mentors
worked when done via FTP, but not via HTTP. (But that may be outdated
information, I haven't tried that in forever.)

Regards,
Christian

Bug#886411: ITP: node-react -- JavaScript library for building user interfaces

[Pirate Praveen]

Package: wnpp
Severity: wishlist
Owner: Pirate Praveen 
X-Debbugs-CC: debian-de...@lists.debian.org
Control: block 886215 by -1
Control: block -1 by 886404

* Package name: node-react
  Version : 16.2.0
  Upstream Author : Facebook, Inc
* URL : https://reactjs.org/
* License : Expat
  Programming Lang: JavaScript
  Description : JavaScript library for building user interfaces

 Some features of React:
  * Declarative: React makes it painless to create interactive UIs.
Design simple
views for each state in your application, and React will efficiently
update and
render just the right components when your data changes. Declarative
views make
your code more predictable, simpler to understand, and easier to debug.
  * Component-Based: Build encapsulated components that manage their own
state, then
compose them to make complex UIs. Since component logic is written
in JavaScript
instead of templates, you can easily pass rich data through your app
and keep
state out of the DOM.
  * Learn Once, Write Anywhere: We don't make assumptions about the rest
of your
technology stack, so you can develop new features in React without
rewriting
existing code. React can also render on the server using Node and
power mobile
apps using React Native.
 .
 Node.js is an event-based server-side JavaScript engine.

In dependency chain for gitlab 9.5 (build dependency of react-dev-utils)



signature.asc
Description: OpenPGP digital signature

Bug#884488: [ktorrent]

[Antonio Marcos López Alonso]

Package: ktorrent
Version: 5.1.0-2

--- Please enter the report below this line. ---

According to:

https://bugs.kde.org/show_bug.cgi?id=387368

a workaround is to disable web search capability, which I did and can confirm 
it works. So severity might be reduced to "Important".

Regards,
Antonio  

--- System information. ---
Architecture: 
Kernel:   Linux 4.14.0-2-amd64

Debian Release: buster/sid
  900 testing ftp.es.debian.org 
  500 stable  update.devolo.com 
  500 stable  kxstudio.linuxaudio.org 
  500 stable  download.videolan.org 
  500 stable  dl.google.com 
  500 sid linux.dropbox.com 
  500 lucid   ppa.launchpad.net 

--- Package information. ---
Depends   (Version) | Installed
===-+-
==
kio | 5.37.0-2
libc6 (>= 2.14) | 
libgcc1  (>= 1:3.0) | 
libgeoip1   | 
libkf5archive5  (>= 4.96.0) | 
libkf5completion5   (>= 4.97.0) | 
libkf5configcore5   (>= 4.98.0) | 
libkf5configgui5(>= 4.97.0) | 
libkf5configwidgets5(>= 4.96.0) | 
libkf5coreaddons5   (>= 5.16.0) | 
libkf5crash5(>= 5.15.0) | 
libkf5dbusaddons5   (>= 4.99.0) | 
libkf5dnssd5(>= 4.96.0) | 
libkf5i18n5 (>= 4.97.0) | 
libkf5iconthemes5   (>= 4.96.0) | 
libkf5itemviews5(>= 4.96.0) | 
libkf5kcmutils5 (>= 4.96.0) | 
libkf5kiocore5  (>= 4.96.0) | 
libkf5kiofilewidgets5   (>= 4.96.0) | 
libkf5kiowidgets5   (>= 4.96.0) | 
libkf5krosscore5(>= 4.96.0) | 
libkf5notifications5(>= 4.96.0) | 
libkf5notifyconfig5 (>= 4.96.0) | 
libkf5parts5(>= 4.96.0) | 
libkf5plotting5 (>= 4.96.0) | 
libkf5service-bin   | 
libkf5service5(>= 5.4.0+git20141113.1055+15.04) | 
libkf5syndication5(>= 15.07.90) | 
libkf5textwidgets5   (>= 5.0.0) | 
libkf5torrent6 (>= 2.1) | 
libkf5webkit5   (>= 4.96.0) | 
libkf5widgetsaddons5(>= 4.96.0) | 
libkf5windowsystem5 (>= 4.96.0) | 
libkf5xmlgui5   (>= 4.98.0) | 
libphonon4qt5-4(>= 4:4.8.0) | 
libqt5core5a(>= 5.9.0~beta) | 
libqt5dbus5  (>= 5.7.0) | 
libqt5gui5   (>= 5.8.0) | 
libqt5network5   (>= 5.7.0) | 
libqt5webkit5 (>= 5.6.0~rc) | 
libqt5widgets5   (>= 5.7.0) | 
libqt5xml5   (>= 5.7.0) | 
libstdc++6 (>= 5.2) | 
libtag1v5   (>= 1.9.1-2.2~) | 
phonon4qt5  | 
ktorrent-data   (= 5.1.0-2) | 
libktorrent-l10n| 


Package's Recommends field is empty.

Suggests(Version) | Installed
=-+-===
krosspython   | 
geoip-database| 20171107-1

Bug#883628: ITP: ioport -- direct access to I/O ports from the command line

[Lubomir Rintel]

On Fri, 5 Jan 2018 12:16:10 +0100 Tobias Frost  wrote:
> On Fri, Jan 05, 2018 at 11:44:55AM +0100, Lubomir Rintel wrote:
> > On Fri, 05 Jan 2018 11:20:02 +0100 Lubomir Rintel 
> > wrote:
> > It's not clear to me what distribution to include in the changelog
> > ("sid", "unstable", "testing" or something else?)
> 
> Use unstable.

Done.

> > Should I be bumping the package version number for each udpate? Should
> > I be adding a new changelog entry for each? Even if not
> > uploaded/released?
> 
> You keep the Debian revision the same until it is sponsored.

That's what I initially meant to do, but mentors.debian.org won't let
me upload a changed package with the same version number.

I suppose I perhaps should've used 1~x version numbers until the
package passes a review, but it doesn't seem to be something I could do
anything about anymore.

> For the 1st upload, you do not add entries to the changelog as well, it
> is just "Initial Packaging (Closes: #ITP-Bug-Number).
> Subsequent uploads will go more into details then, listing every change
> made to the packaging.

> I recommend to browse through the documents linked in "3. Make the package"
> in https://mentors.debian.net/intro-maintainers. They will probably help you
> a lot to get into the (difficult) topic of packaging.
> I know its a lot to read, but it helps to know "where to look"; it is not
> necessary that you memorize everything to the letter, but a rough idea where
> something is explained will help. (and the knowledge will also come with
> using it anyway)

Yeah, I'm familiar with it (the link, not necessarily the content).

Still, while probably a great reference, the documentation doesn't seem
to be too good at providing best practices guidance (should the package
be versioned in a VCS? Should I pick any hosting or is it typical to
keep it on alioth/salsa? Should I always be relying on latest
debhelper? Etc.). I suppose that builds up with experience.

The updated package:

https://mentors.debian.net/debian/pool/main/i/ioport/ioport_1.2-4.dsc

Thanks
Lubo

Bug#886409: ITP: flameshot -- Powerful yet simple screenshot software

[Boyuan Yang]

Package: wnpp
Severity: wishlist
Owner: Boyuan Yang <073p...@gmail.com>
X-Debbugs-CC: i...@hotmail.es

* Package name: flameshot
  Version : 0.5.0
  Upstream Author : lupoDharkael 
* URL : https://github.com/lupoDharkael/flameshot
* License : GPL-3
  Programming Lang: C++/Qt
  Description : Powerful yet simple screenshot software

I intend to package and maintain "flameshot" inside Debian.

Flameshot is a powerful yet simple-to-use screenshot software. Notable 
features include customizable appearance, in-app screenshot editing, D-Bus 
interface, experimental GNOME/KDE Wayland support, integration with Imgur and 
support for both GUI and CLI interface.

I intend to co-maintain it inside Salsa's Debian group [2], also applicable to 
LowNMU [1].

[1] https://wiki.debian.org/LowThresholdNmu
[2] https://salsa.debian.org/Debian/

Regards,
Boyuan Yang

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

Bug#886404: need help with build error

[Pirate Praveen]

Control: tags -1 help

code is here https://salsa.debian.org/js-team/node-rollup-plugin-babel

since rollup is not in main, trying to use webpack, but getting this error.

webpack --config debian/webpack.config.js \
--target node \
--output-library-target=commonjs \
src/index.js dist/rollup-plugin-babel.cjs.js
Hash: bb9073a32e1a797a8c70
Version: webpack 3.5.6
Time: 6970ms
 Asset Size  ChunksChunk Names
rollup-plugin-babel.cjs.js  1.48 MB   0  [emitted]  [big]  main
 [151] /usr/lib/nodejs/babel-core/index.js 46 bytes {0} [built]
 [152] /usr/lib/nodejs/babel-core/lib/api/node.js 4.34 kB {0} [built]
 [242] ./src/constants.js 121 bytes {0} [built]
 [243] ./src/index.js 3.11 kB {0} [built]
 [534] /usr/lib/nodejs/babel-core/lib/tools/build-external-helpers.js
3.64 kB {0} [built]
 [535] /usr/lib/nodejs/babel-core/package.json 303 bytes {0} [built]
[failed] [1 error]
 [536] /usr/lib/nodejs/babel-core/lib/transformation/pipeline.js 2.19 kB
{0} [built]
 [538] /usr/lib/nodejs/rollup-pluginutils/index.js 438 bytes {0} [built]
 [539] /usr/lib/nodejs/rollup-pluginutils/addExtension.js 197 bytes {0}
[built]
 [540] /usr/lib/nodejs/rollup-pluginutils/attachScopes.js 3.17 kB {0}
[built]
 [542] /usr/lib/nodejs/rollup-pluginutils/createFilter.js 939 bytes {0}
[built]
 [600] /usr/lib/nodejs/rollup-pluginutils/makeLegalIdentifier.js 1.28 kB
{0} [built]
 [601] ./src/preflightCheck.js 1.35 kB {0} [built]
 [602] ./src/helperPlugin.js 662 bytes {0} [built]
 [603] ./src/utils.js 115 bytes {0} [built]
+ 589 hidden modules

WARNING in
/usr/lib/nodejs/babel-core/lib/transformation/file/options/option-manager.js
190:19-37 Critical dependency: the request of a dependency is an expression

WARNING in
/usr/lib/nodejs/babel-core/lib/transformation/file/options/option-manager.js
307:16-34 Critical dependency: the request of a dependency is an expression

WARNING in /usr/lib/nodejs/base/utils.js
3:34-41 Critical dependency: require function is used in a way in which
dependencies cannot be statically extracted

WARNING in /usr/lib/nodejs/use/utils.js
3:34-41 Critical dependency: require function is used in a way in which
dependencies cannot be statically extracted

WARNING in /usr/lib/nodejs/babel-core/lib/transformation/file/index.js
511:24-39 Critical dependency: the request of a dependency is an expression

WARNING in /usr/lib/nodejs/babel-core/lib/transformation/file/index.js
710:16-34 Critical dependency: the request of a dependency is an expression

WARNING in /usr/lib/nodejs/is-descriptor/utils.js
7:34-41 Critical dependency: require function is used in a way in which
dependencies cannot be statically extracted

ERROR in /usr/lib/nodejs/globals/globals.json
Module build failed: SyntaxError: Unexpected token, expected ; (2:10)

  1 | {
> 2 |   "builtin": {
|^
  3 |   "Array": false,
  4 |   "ArrayBuffer": false,
  5 |   "Boolean": false,

 @ /usr/lib/nodejs/globals/index.js 1:17-42
 @ /usr/lib/nodejs/babel-traverse/lib/scope/index.js
 @ /usr/lib/nodejs/babel-traverse/lib/index.js
 @ /usr/lib/nodejs/babel-core/lib/api/node.js
 @ /usr/lib/nodejs/babel-core/index.js
 @ ./src/index.js

ERROR in /usr/lib/nodejs/babel-core/package.json
Module build failed: SyntaxError: Unexpected token, expected ; (2:8)

  1 | {
> 2 |   "name": "babel-core",
| ^
  3 |   "version": "6.25.0",
  4 |   "description": "Babel compiler core.",
  5 |   "author": "Sebastian McKenzie ",

 @ /usr/lib/nodejs/babel-core/lib/api/node.js 60:15-39
 @ /usr/lib/nodejs/babel-core/index.js
 @ ./src/index.js



signature.asc
Description: OpenPGP digital signature

Bug#883628: ITP: ioport -- direct access to I/O ports from the command line

[gregor herrmann]

On Fri, 05 Jan 2018 12:07:28 +0100, Tobias Frost wrote:

> Note that dch(1) when invoked with "-r" will do that for you,
> along with updating the timestamp. (note that dch will throw away
> it when you do not edit anything in the log, workaround is 'dch -r ""')

Unless you set "DEBCHANGE_FORCE_SAVE_ON_RELEASE=no" in ~/.devscripts.

From /usr/share/doc/devscripts/devscripts.conf.ex :

# When --release was used and an editor presented, force the changelog
# to be explicitly saved in the editor?  If this is set to "no" then
# the changes made by --release will be automatically saved.
# DEBCHANGE_FORCE_SAVE_ON_RELEASE=yes


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Beatles


signature.asc
Description: Digital Signature

Bug#866973: cyrus-imapd 3.0 needs to be (eventually) packaged

[Dan White]

Ond,

I may have some time the week after next to assist. Any contributions I'd
have would be external.

On 01/05/18 11:41 +0100, Ondřej Surý wrote:

Yes, the maintainer is active.

I started cyrus-imapd 3.0 packaging while ago and it's noticeable amount
of work, so if anybody else want to join the packaging team and do the
heavylifting before a bigger time window of free time opens for me, they
would be welcome.

I would be happy to convert the cyrus-imapd packaging to salsa.debian.org,
so it's easier for external contributors to add code.

O.
--
Ondřej Surý 

On Mon, Jan 1, 2018, at 20:36, Berhardt Eckl wrote:

Does anybody know if maintainer is still active on this package? Is
there any reason why updates are not packaged?

Thx

Bug#886241: [Pkg-xfce-devel] Bug#886241: config file directories hidden in /usr/share/lightdm

[Yves-Alexis Perez]

On Fri, 2018-01-05 at 14:29 +0100, Harald Dunkel wrote:
> The man pages don't mention these config files in /usr, i.e. you get
> weird effects due to some undocumented config files.

What do you mean by “weird effect”?
> 
> Its unexpected (esp. since /etc/lightdm/ can be found in the usual
> directory) and it doesn't follow the policy. The policy is very strict
> in this case:

What is unexpected? 

In any case, you can just override anything you want with your own
configuration in /etc, and it'll preserved.
> 
> 
> Any configuration files created or used by your package must reside in
> /etc. If there are several, consider creating a subdirectory of /etc
> named after your package.

Configuration file here means something you can modify and hope to keep
accross package upgrade. It's common for packages to have default
configuration (distribution-default) in /usr, overridable by the local admin
with file in /etc. See the whole Xfce stack, systemd, whatever.
> 
> If your package creates or uses configuration files outside of /etc,
> and it is not feasible to modify the package to use /etc directly, put
> the files in /etc and create symbolic links to those files from the
> location that the package requires.

> 
> Is this unreasonable or invalid in this case?

Your reading is invalid.

Regards,
-- 
Yves-Alexis

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

Bug#732011: O: gyrus -- GNOME tool for Cyrus-IMAP servers administration

[Willem van den Akker]

Hi,

I am using Gyrus and will adopting it.

/Willem

Bug#886408: New mailing list: debian-mate

[Mike Gabriel]

Package: lists.debian.org
Severity: wishlist
X-Debbugs-Cc: pkg-mate-t...@lists.alioth.debian.org

Dear list admins,

Please provide a Alioth replacement list for the Debian MATE Packaging Team.

Name: debian-mate (@lists.d.o)
Rationale:

  The list will be used for user and developer discussions around the
  MATE Desktop Environment as it is found in Debian. We also plan to
  switch the MATE related pkgs' maintainer address field to this list.

Short description: Debian MATE Packaging Team

Category: Developers

Subscription Policy: open

Web Archive: yes

Moving existing mailing lists to lists.debian.org:

  Ideally the pkg-mate-team mailing list should be ported to this list [1].
  Can the list content be obtained internally by the listadmins? Or do I need
  to provide list members and archive mbox(es)?


Thanks,
Mike

[1] http://lists.alioth.debian.org/cgi-bin/mailman/admin/pkg-mate-team
--

mike gabriel aka sunweaver (Debian Developer)
mobile: +49 (1520) 1976 148
landline: +49 (4354) 8390 139

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: sunwea...@debian.org, http://sunweavers.net



pgptmxAhJdU97.pgp
Description: Digitale PGP-Signatur

Bug#886407: New mailing list: debian-remote

[Mike Gabriel]

Package: lists.debian.org
Severity: wishlist
X-Debbugs-Cc: pkg-remote-t...@lists.alioth.debian.org

Dear list admins,

Please provide a Alioth replacement list for the Debian Remote  
Maintainers Team.


Name: debian-remote (@lists.d.o)
Rationale:

  The list will be used for developer discussions around Debian as a remote
  desktop system. It will also be used as maintainer address in packages
  maintained by the Debian Remote Team.

Short description: Debian Remote Maintainers Team

Category: Developers

Subscription Policy: open

Web Archive: yes

Moving existing mailing lists to lists.debian.org:

  Ideally the pkg-remote-team mailing list should be ported to this list [1].
  Can the list content be obtained internally by the listadmins? Or do I need
  to provide list members and archive mbox(es)?


Thanks,
Mike

[1] http://lists.alioth.debian.org/cgi-bin/mailman/admin/pkg-remote-team
--

mike gabriel aka sunweaver (Debian Developer)
mobile: +49 (1520) 1976 148
landline: +49 (4354) 8390 139

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: sunwea...@debian.org, http://sunweavers.net



pgpzlyi2Xpwfr.pgp
Description: Digitale PGP-Signatur

Bug#882247:

[積丹尼 Dan Jacobson]

As there is no United States version
$ apt-cache search firefox|grep English
firefox-l10n-en-gb - English (United Kingdom) language package for Firefox
firefox-l10n-en-za - English (South Africa) language package for Firefox
I'll just wait.

Bug#886406: PID file directory not created by init script

[Kilian Krause]

Package: burp
Version: 2.0.54-1
Severity: normal

Hi,

When trying to start burp automatically upon boot the PID file directory
isn't automatically created, resulting in:

root@backup:~# service burp status
* burp.service - LSB: backup and restore program
   Loaded: loaded (/etc/init.d/burp; generated; vendor preset: enabled)
   Active: active (exited) since Fri 2018-01-05 11:40:28 CET; 2h 8min ago
 Docs: man:systemd-sysv-generator(8)
Tasks: 0 (limit: 4915)
   CGroup: /system.slice/burp.service

Jan 05 11:40:28 backup systemd[1]: Starting LSB: backup and restore program...
Jan 05 11:40:28 backup burp[701]: Could not open lock file 
/var/run/burp/burp.server.pid: No such file or directory
Jan 05 11:40:28 backup burp[701]: Could not get lockfile.
Jan 05 11:40:28 backup burp[701]: Maybe you do not have permissions to write to 
/var/run/burp/burp.server.pid.
Jan 05 11:40:28 backup burp[663]: Starting burp : failed!
Jan 05 11:40:28 backup systemd[1]: Started LSB: backup and restore program.
root@backup:~#

Since this seems to be a race condition, starting the daemon with the
same script later does work ok:
root@backup:~# service burp restart
root@backup:~# service burp status
* burp.service - LSB: backup and restore program
   Loaded: loaded (/etc/init.d/burp; generated; vendor preset: enabled)
   Active: active (running) since Fri 2018-01-05 13:48:56 CET; 1s ago
 Docs: man:systemd-sysv-generator(8)
  Process: 5928 ExecStop=/etc/init.d/burp stop (code=exited, status=0/SUCCESS)
  Process: 5936 ExecStart=/etc/init.d/burp start (code=exited, status=0/SUCCESS)
Tasks: 1 (limit: 4915)
   CGroup: /system.slice/burp.service
   `-5945 /usr/sbin/burp -c /etc/burp/burp-server.conf

Jan 05 13:48:56 backup systemd[1]: Stopped LSB: backup and restore program.
Jan 05 13:48:56 backup systemd[1]: Starting LSB: backup and restore program...
Jan 05 13:48:56 backup burp[5936]: Starting burp :.
Jan 05 13:48:56 backup systemd[1]: Started LSB: backup and restore program.
root@backup:~#

Maybe this should be circumvented by creating a systemd service with proper
dependency chain or just hotfixed by the init script creating the required
directory before the start-stop-daemon.

Best,
Kilian

Bug#886405: bumblebee-nvidia: optirun/primus seems to work, but no display output

[Brainslug]

Package: bumblebee-nvidia
Version: 3.2.1-17
Severity: normal

Dear Maintainer,

I am trying to get optirun/primusrun to work on a Dell Precision M4800
laptop which has Optimus capabilities and the following hardware:

brainslug@m4800:~$ lspci
...
00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core
Processor Integrated Graphics Controller (rev 06)
...
01:00.0 VGA compatible controller: NVIDIA Corporation GK107GLM [Quadro
K1100M] (rev ff)


I've installed bumblebee-nvidia and primus packages 3.2.1-17, running
kernel 4.14.0-2-amd64, no multi-arch, Debian testing. No external
displays connected, only internal laptop display used.


optirun/primusrun seems to work for some programs, like darktable &
bash, but for most programs I don't get any display output, examples
include firefox, glxgears, glxinfo.


According to syslog the Nvidia card gets activated and I can see that
/proc/acpi/bbswitch changes from "OFF" to "ON" during
a primusrun/optirun attempt. I just don't see the program output.


Some debug info below - if this bug report should be filed against
another package, please let me know. Any help would be much appreciated.


Initial state:

brainslug@m4800:~$ cat /proc/acpi/bbswitch
:01:00.0 OFF

then

brainslug@m4800:~$ optirun -v glxinfo
[  552.198375] [INFO]Response: Yes. X is active.

[  552.198392] [INFO]Running application using primus.
^C[  605.131876] [WARN]Received Interrupt signal.

while running, this in other shell:

brainslug@m4800:~$ cat /proc/acpi/bbswitch
:01:00.0 ON

Then after the command is terminated via Ctrl-C:

brainslug@m4800:~$ cat /proc/acpi/bbswitch
:01:00.0 OFF

from syslog:

Jan  6 02:09:17 m4800 kernel: [  550.267976] bbswitch: enabling discrete
graphics
Jan  6 02:09:18 m4800 kernel: [  551.049385] nvidia :01:00.0:
vgaarb: changed VGA decodes: olddecodes=none,decodes=none:owns=none
Jan  6 02:09:18 m4800 kernel: [  551.049448] nvidia-nvlink: Nvlink Core
is being initialized, major device number 243
Jan  6 02:09:18 m4800 kernel: [  551.049456] NVRM: loading NVIDIA UNIX
x86_64 Kernel Module  375.82  Wed Jul 19 21:16:49 PDT 2017 (using threaded \
interrupts)
Jan  6 02:09:19 m4800 acpid: client connected from 3275[0:999]
Jan  6 02:09:19 m4800 acpid: 1 client rule loaded
Jan  6 02:09:19 m4800 kernel: [  551.788227] nvidia-modeset: Loading
NVIDIA Kernel Mode Setting Driver for UNIX platforms  375.82  Wed Jul 19
20:3\
5:11 PDT 2017
Jan  6 02:09:19 m4800 bumblebeed[992]: [  552.198276] [WARN][XORG] (WW)
`fonts.dir' not found (or not valid) in "/usr/share/fonts/X11/Type1".
Jan  6 02:09:19 m4800 bumblebeed[992]: [  552.198293] [WARN][XORG] (WW)
NVIDIA(0): Unable to get display device for DPI computation.
Jan  6 02:09:19 m4800 bumblebeed[992]: [  552.198301] [ERROR][XORG] (EE)
PreInit returned 2 for ""
Jan  6 02:10:12 m4800 kernel: [  605.250609] nvidia-modeset: Unloading
Jan  6 02:10:12 m4800 acpid: client 3275[0:999] has disconnected
Jan  6 02:10:12 m4800 kernel: [  605.283041] nvidia-nvlink: Unregistered
the Nvlink Core, major device number 243
Jan  6 02:10:12 m4800 kernel: [  605.316555] bbswitch: disabling
discrete graphics
Jan  6 02:10:12 m4800 kernel: [  605.334899] pci :01:00.0: Refused
to change power state, currently in D0

I've also tried to specify the display explicitly, like so:

brainslug@m4800:~$ optirun -v -d :0 -b primus glxinfo

but the results are the same -- no glxinfo output.


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

Kernel: Linux 4.14.0-2-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 bumblebee-nvidia depends on:
ii  bumblebee   3.2.1-17
ii  glx-alternative-nvidia  0.8.0
ii  nvidia-kernel-dkms  375.82-7

bumblebee-nvidia recommends no packages.

bumblebee-nvidia suggests no packages.

-- no debconf information

Bug#886241: [Pkg-xfce-devel] Bug#886241: config file directories hidden in /usr/share/lightdm

[Harald Dunkel]

The man pages don't mention these config files in /usr, i.e. you get
weird effects due to some undocumented config files.

Its unexpected (esp. since /etc/lightdm/ can be found in the usual
directory) and it doesn't follow the policy. The policy is very strict
in this case:


Any configuration files created or used by your package must reside in
/etc. If there are several, consider creating a subdirectory of /etc
named after your package.

If your package creates or uses configuration files outside of /etc,
and it is not feasible to modify the package to use /etc directly, put
the files in /etc and create symbolic links to those files from the
location that the package requires.


Is this unreasonable or invalid in this case?


Regards
Harri

Bug#884802: [Pkg-xfce-devel] Bug#884802: xfce4-panel: Undeletable buttons of nonexistent processes.

[Lorenzo Ancora]

Hello,
since you are having problems in reproducing the bug and the crash is
predictable, I suspect that these are symptoms of a hidden memory
corruption in a library.
My theory is that while using Openbox the panel does not access an
invalid pointer (probably thanks to some abstractions) but with xfwm4 it
does. This problem is the same but in the 1st case it remains hidden.

To verify my theory I replaced Openbox with xfwm4 and killed compton and
all the desktop gadgets.
Then I repeated all the actions of the video and the panel crashed and
restarted itself.

To debug the panel I killed xfce4-panel and executed it under dgb. Even
without the debug symbols I discovered
the position of the bug: "tasklist-widget.c" @ line 2681. This should
be, at least, a good place to start.

GDB's OUTPUT: https://paste.debian.net/1003593

If I can do something else, I'll be glad to help.

Regards,
Lorenzo

Bug#886404: ITP: node-rollup-plugin-babel -- Seamless integration between Rollup and Babel

[Pirate Praveen]

Package: wnpp
Severity: wishlist
Owner: Pirate Praveen 
X-Debbugs-CC: debian-de...@lists.debian.org

* Package name: node-rollup-plugin-babel
  Version : 3.0.3
  Upstream Author : Rich Harris
* URL : https://github.com/rollup/rollup-plugin-babel
* License : Expat
  Programming Lang: JavaScript
  Description : Seamless integration between Rollup and Babel

 If you're using Babel to transpile your ES6/7 code and Rollup to generate a
 standalone bundle, you have a couple of options:
  * run the code through Babel first, being careful to exclude the module
transformer, or
  * run the code through Rollup first, and *then* pass it to Babel.
 .
 Both approaches have disadvantages. Using Rollup with
rollup-plugin-babel makes the
 process far easier.
 .
 Node.js is an event-based server-side JavaScript engine.

In dependency chain of gitlab 9.5 (build dependency of react).



signature.asc
Description: OpenPGP digital signature

Bug#886316: gcc-7: fix typo for N32 conditions in debian/rules2

[YunQiang Su]

Ohhh, you are right.

in fact it is a quite simple patch:

just in debian/rules2, there are 4 snap
$(biarchn32)-$(biarch32) for N32,

the $(biarchn32) should be $(biarch64) here.

On Thu, Jan 4, 2018 at 8:22 PM, James Cowgill  wrote:
> Hi,
>
> On 04/01/18 11:00, YunQiang Su wrote:
>> Package: src:gcc-7
>> Version: 7.2.0-18
>>
>> when detect mipsn32 triarch,
>> we use ifeq ($(biarchn32)-$(biarch32),yes-yes), but we should use
>>   ifeq ($(biarch64)-$(biarch32),yes-yes)
>>
>
> I guess you attached the wrong patch?
>
> James
>



-- 
YunQiang Su

Bug#886368: intel-microcode: copyright URLs out of date

[Henrique de Moraes Holschuh]

On Thu, 04 Jan 2018, Matt Taggart wrote:
> The two upstream download URLs listed in the copyright file no longer work
> (and are also http URLs). Searching I found the following
> 
> https://downloadcenter.intel.com/download/27337/Linux-Processor-Microcode-Data-File
> 
> but I suspect that URL might be specific to the 20171117 version.
> Hopefully you can find a more generic URL for the latest version.

Try the upstream URL in the control file, it works (for now, at least),
although I noticed there is an up to 24h delay between a release, and it
showing up in the search engine:

https://downloadcenter.intel.com/search?keyword=linux+microcode

I need to update that copyright file, but either it will piss me off to
no end by requiring an update at every new upstream release, or I will
just place an useless URL there that requires human + browser +
javascript to be converted into an usable download.  meh.

-- 
  Henrique Holschuh

Bug#886382: Coming updates for meltdown/spectre

[Henrique de Moraes Holschuh]

On Fri, 05 Jan 2018, Louis-Philippe Véronneau wrote:
> Package: amd64-microcode
> Severity: grave
> 
> It seems AMD cpus are also affected by the meltdown/spectre bugs.

Yes, they are, although just by Spectre as far as we know (i.e. not
affected by Meltdown).

> Do you know if AMD plans to release microcode updates and if so, will it
> be packaged here?

Yes, they will release microcode updates to vendors.  Apparently, these
are not ready yet.

No, we don't know if they will release it *only* to vendors for a
firmware update, or also for operating system updates.  Also, for Zen
and later one cannot just hope to update microcode through the operating
system, often it requires such an early update that it has to be done by
the firmware itself.

Therefore, this bug is not actionable right now.  I will leave it open,
but there is absolutely nothing we can do about it at the moment.

Pester your motherboard vendor for an expected timeline for fixes, and
do keep in mind that everyone had scheduled themselves for the issue to
be disclosed next week (2018-01-09), not on 2018-01-03, so some leeway
should be given for any vendor that is only going to have its stuff
ready by next week.

-- 
  Henrique Holschuh

Bug#859867: [buildd-tools-devel] Bug#859867: Please add a package which automatically configures sbuild for Debian packaging

[Raphael Hertzog]

On Fri, 05 Jan 2018, Michael Stapelberg wrote:
> Raphaël, Benjamin, what’s the current status? It’s been quite a number
> of months since https://bugs.debian.org/859867#122, and I’m still very
> interested in having sbuild easily installable.

Benjamin never answered on the willingness to host this new infrastructure
within packaging-dev.

As for me, while I'm still supportive of the idea, I'm afraid that I won't
be able to contribute code in the near future. I have other priorities
related to tracker.debian.org. Hopefully my ideas will help you design
something modular enough to cover the needs of derivatives. Please keep
me in the loop, I might be able to help once it becomes a bit more
concrete and then I might be able to invest some time as part of my work
on Kali.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: https://www.freexian.com/services/debian-lts.html
Learn to master Debian: https://debian-handbook.info/get/

Bug#886389: dpkg: conffile marked as obsolete after being taken over by different package

[Guillem Jover]

Hi!

On Fri, 2018-01-05 at 10:55:50 +0100, Sven Joachim wrote:
> On 2018-01-05 10:44 +0100, Sven Joachim wrote:
> 
> > Package: dpkg
> > Version: 1.19.0.4
> > Severity: normal
> >
> > After switching from rxvt-unicode-256color to rxvt-unicode (see
> > #848284), dpkg-query reports a conffile as obsolete:
> >
> > ,
> > | $ dpkg-query -W -f='${Conffiles}\n' | grep obsolete$
> > |  [...]
> > |  /etc/X11/app-defaults/URxvt 7b221a2da49507e31f42e702791b085b obsolete
> > | $ dpkg -S /etc/X11/app-defaults/URxvt 
> > |  rxvt-unicode: /etc/X11/app-defaults/URxvt
> > `
> >
> > This is bogus since the file is shipped in the package, otherwise it
> > would belong to rxvt-unicode-256color which was its previous owner.

This does not show what package owned that obsolete entry, though. But
in principle that should have been rxvt-unicode-256color. Both packages
will have such conffiles listed in their Conffiles fields, but the old
one might have an obsolete entry, which will be ignored by dpkg for
most operations.

> Purging the rxvt-unicode-256color package helped, although that package
> did not contain any files according to "dpkg -L" (I had already removed
> but not purged it).  Now the conffile is no longer reported as obsolete.

Was going to ask for the -s output for both packages, but it's too
late now. :) Well, barring reinstalling the older package.

Thanks,
Guillem

Bug#886393: doesn't clean up inherited children

[Wouter Verhelst]

On Fri, Jan 05, 2018 at 01:10:21PM +0100, Uli Schlachter wrote:
> Hi,
> 
> On 05.01.2018 11:45, Wouter Verhelst wrote:
> > If you need further information, do ask.
> 
> How would you fix this?
> 
> Awesome uses glib. Your favorite search engine can provide you with lots
> of information on the problems here (e.g. [1,2]), but it boils down to:
> This is not possible with glib. GLib only reaps children that it starts
> itself and does not provide an API to take over SIGCHLD handling.

Er, you could then stop using GLib to spawn children? ;-)

nbd-server uses glib too, but doesn't use g_spawn_sync or any of the other
problematic APIs, and catches SIGCHLD just fine.

-- 
Could you people please use IRC like normal people?!?

  -- Amaya Rodrigo Sastre, trying to quiet down the buzz in the DebConf 2008
 Hacklab

Bug#886387: closed by Mehdi Dogguy <me...@debian.org> (Bug#886387: fixed in mstflint 4.8.0-2)

[Mehdi Dogguy]

reopen 886387
found 886387 linux/4.14.7-1~bpo9+1
kthxbye

On Fri, Jan 05, 2018 at 11:51:07AM +, Debian Bug Tracking System 
 wrote:
>  mstflint (4.8.0-2) unstable; urgency=medium
>  .
>* Make the build reproducible (Closes: #886387). Thanks to Chris Lamb
>  for the patch.
>  - add 0012-Reproducible-build.patch

I made a typo in the changelog and closed the wrong bug. Sorry for that. I am
opening it again.

Regards,

-- 
Mehdi Dogguy

Bug#886399: RFS: opencascade/7.2.0-2 [ITP]

[Tobias Frost]

Hi Kurt Kremitzki,

many thanks for the package!

As the package is huge, I think review will take some time and probably
some iterations. I will start on the review, but I hope that others
will chime in. (I will not have enough time for a complete review
today)

- d/README.Debian.html
I'm not sure if we want a html file as README.debian. It seems also
quite outdates (referring to version 6.5). Its content is also covered
by other parts of the pacakging (e.g by d/control), so I guess it
should be deleted
- d/README.source
Same here, quilt is standard nowardays, so it can be retired.
I'm not sure about the repacking part, but if that is still true,
the package version would needs to be a -dfsg anyway.
- d/changelog
Please keep at Debian revision -1 until this is sponsored.
But as this is a reintroduction of an old package, you will
still need to record all the changes you have made to the old
packaging.
(There is also extra blank lines below your entries)
- d/compat: Did you see if you can use compat level 11?
- please add dep3 headers to the patches.

- d/control
  - VCS-* are for the Debian packaging, not for the upstream
repository.
  - Would be great if you could maintain the package on a git repo; you
can use salsa.debian.org for it.


Sofar...
I try to dedicate some more time later...

Bug#886212: pure-ftpd FTCBFS: configures for the build architecture

[Stefan Hornburg (Racke)]

On 01/03/2018 08:21 AM, Helmut Grohne wrote:
> Source: pure-ftpd
> Version: 1.0.46-1
> Tags: patch
> User: helm...@debian.org
> Usertags: rebootstrap
> 
> pure-ftpd fails to cross build from source, because it does not pass the
> required --host flag to ./configure. The easiest way of doing that is
> deferring the task to dh_auto_configure. After doing so, pure-ftpd still
> fails to cross build, because it uses AC_RUN_IFELSE without a default.
> Most of the checks can be converted to AC_COMPILE_IFELSE or
> AC_LINK_IFELSE with little loss, but that requires autoreconfing the
> package and that is quite difficult to achieve with the current
> packaging. Thus I ask you to just apply the attached patch and closing
> this bug when doing so to make the AC_RUN_IFELSE issue apparent to cross
> builders. It would also be nice to run autoreconf to be able to fix the
> other issues.
> 
> Helmut
> 

Hello Helmut,

I'm going to upload packages with this fix applied on this weekend.

Regards
Racke

-- 
Ecommerce and Linux consulting + Perl and web application programming.
Debian and Sympa administration. Provisioning with Ansible.

Bug#886393: doesn't clean up inherited children

[Uli Schlachter]

Hi,

On 05.01.2018 11:45, Wouter Verhelst wrote:
> If you need further information, do ask.

How would you fix this?

Awesome uses glib. Your favorite search engine can provide you with lots
of information on the problems here (e.g. [1,2]), but it boils down to:
This is not possible with glib. GLib only reaps children that it starts
itself and does not provide an API to take over SIGCHLD handling.

Cheers,
Uli

[1]: https://bugzilla.xamarin.com/show_bug.cgi?id=21818
[2]: https://bugzilla.redhat.com/show_bug.cgi?id=981580

Bug#880407: #880407 xterm: font issue with FreeType 2.8; should not use the rounded ascender and descender

[Vincent Lefevre]

On 2018-01-05 05:21:32 -0500, Thomas Dickey wrote:
> On Fri, Jan 05, 2018 at 10:26:11AM +0100, Vincent Lefevre wrote:
> > Sorry, I don't understand what you mean. Can you reproduce the problem
> > with that?
> 
> only for the case that I made xterm detect/workaround.
> 
> I added debug-tracing in fontutils.c to show the actual data for the
> FT_Size_Metrics, as well as loading the glyph to see the pixels.
> It wasn't a "black" line but rather two raster lines with low values.
> 
> The rounding change altered the weights from about 12/16 down to 8/16
> or 9/16.
> 
> I added logic to add the weights and turn on xterm's line-drawing when
> it fell below the threshold.

But I assume that this wouldn't fix the window height (the cells
are 23-pixel high instead of 21).

I have tried with -xrm "*scaleHeight: 0.9", which gives the same
height as before (21 pixels per cell), but this doesn't make these
blank lines disappear. Moreover, when I type "É" (E with an acute
accent), the accent is no longer visible!

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#886402: needrestart: Shows perl errors (uninitialized value)

[cretox]

On Fri, 05 Jan 2018 12:54:08 +0100
cre  wrote:
> The program seems to run fine, but it prints out these error messages
> just before the "real" messages:
> 
> $ sudo needrestart 
> [sudo] password for cre: 
> Use of uninitialized value $testp in stat
> at /usr/sbin/needrestart line 462,  line
> 1.==  ] Use of uninitialized value $sdev in right
> bitshift (>>) at /usr/sbin/needrestart line 463,  line 1. Use
> of uninitialized value $sdev in right bitshift (>>)
> at /usr/sbin/needrestart line 463,  line 1. Use of
> uninitialized value $sdev in bitwise and (&) at /usr/sbin/needrestart
> line 463,  line 1. Use of uninitialized value $sdev in right
> bitshift (>>) at /usr/sbin/needrestart line 463,  line 1. Use
> of uninitialized value $sdev in right bitshift (>>)
> at /usr/sbin/needrestart line 463,  line 1. Use of
> uninitialized value $sdev in bitwise and (&) at /usr/sbin/needrestart
> line 463,  line 1. Use of uninitialized value $sdev in right
> bitshift (>>) at /usr/sbin/needrestart line 475,  line 1. Use
> of uninitialized value $sdev in right bitshift (>>)
> at /usr/sbin/needrestart line 475,  line 1. Use of
> uninitialized value $sinode in string eq at /usr/sbin/needrestart
> line 480,  line 1. Scanning processes... Scanning candidates...
> Scanning linux images... [...cut...]
> 
> That seems related to perl.

Setting

$nrconf{skip_mapfiles} = (-d '/proc/sys/kernel/grsecurity' ? -1 : 1);

solves the issue but disables the check?

-- 
cre

Bug#886403: zfs-linux: Please update to latest version 0.7.5

[Holger Schröder]

Source: zfs-linux
Severity: wishlist

Dear Maintainer,

please update to latest version 0.7.5

Greetings
Holger...



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

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

Bug#886394: java.lang.ClassNotFoundException: javafx.scene.layout.HBox

[Markus Koschany]

Control: severity -1 important


Am 05.01.2018 um 11:55 schrieb Ludovic CHEVALIER:
> Package: pdfsam
> Version: 3.3.5-1
> Severity: grave
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
> I can't launch pdfsam. Here is the traceback:
> 
> Exception in thread "main" java.lang.NoClassDefFoundError: 
> javafx/scene/layout/HBox
>   at java.base/java.lang.ClassLoader.defineClass1(Native Method)
>   at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1007)
>   at 
> java.base/java.security.SecureClassLoader.defineClass(SecureClassLoader.java:174)
>   at 
> java.base/jdk.internal.loader.BuiltinClassLoader.defineClass(BuiltinClassLoader.java:801)
>   at 
> java.base/jdk.internal.loader.BuiltinClassLoader.findClassOnClassPathOrNull(BuiltinClassLoader.java:699)
>   at 
> java.base/jdk.internal.loader.BuiltinClassLoader.loadClassOrNull(BuiltinClassLoader.java:622)
>   at 
> java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:580)
>   at 
> java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:185)
>   at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:496)
>   at org.pdfsam.community.App.main(App.java:34)
> Caused by: java.lang.ClassNotFoundException: javafx.scene.layout.HBox
>   at 
> java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:582)
>   at 
> java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:185)
>   at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:496)
>   ... 10 more

Hello,

thanks for reporting. PDFsam works for me with OpenJDK 8 but I can
reproduce this issue with OpenJDK 9. The class javafx.scene.layout.HBox
should be present in libopenjfx-java but I presume we need to adjust the
openjfx package for Java 9 to make it work.

Regards,

Markus





signature.asc
Description: OpenPGP digital signature

Bug#886402: needrestart: Shows perl errors (uninitialized value)

[cre]

Package: needrestart
Version: 2.11-4
Severity: normal

Dear Maintainer,

The program seems to run fine, but it prints out these error messages just 
before the "real" messages:

$ sudo needrestart 
[sudo] password for cre: 
Use of uninitialized value $testp in stat at /usr/sbin/needrestart line 
462,  line 1.==  ]
Use of uninitialized value $sdev in right bitshift (>>) at 
/usr/sbin/needrestart line 463,  line 1.
Use of uninitialized value $sdev in right bitshift (>>) at 
/usr/sbin/needrestart line 463,  line 1.
Use of uninitialized value $sdev in bitwise and (&) at 
/usr/sbin/needrestart line 463,  line 1.
Use of uninitialized value $sdev in right bitshift (>>) at 
/usr/sbin/needrestart line 463,  line 1.
Use of uninitialized value $sdev in right bitshift (>>) at 
/usr/sbin/needrestart line 463,  line 1.
Use of uninitialized value $sdev in bitwise and (&) at 
/usr/sbin/needrestart line 463,  line 1.
Use of uninitialized value $sdev in right bitshift (>>) at 
/usr/sbin/needrestart line 475,  line 1.
Use of uninitialized value $sdev in right bitshift (>>) at 
/usr/sbin/needrestart line 475,  line 1.
Use of uninitialized value $sinode in string eq at /usr/sbin/needrestart 
line 480,  line 1.
Scanning processes...
Scanning candidates...
Scanning linux images...
[...cut...]

That seems related to perl.


-- Package-specific info:
needrestart output:
Your outdated processes:
applet.py[1317], at-spi-bus-laun[1251], at-spi2-registr[1258], bash[21570], 
claws-mail[21747], dbus-daemon[1256, 1174], dconf-service[1342], 
firefox[21585], gvfsd[1306], keepassxc[21528],
 light-locker[1324], panel-2-actions[1302], panel-4-notific[1301], 
panel-6-systray[1300], panel-7-whisker[1289], panel-12-cpugra[1296], 
panel-16-fsguar[1299], panel-17-netloa[1298],
 panel-19-system[1297], pulseaudio[1318], sh[1166], systemd[1150], 
terminator[21561], Thunar[1271], VBoxClient[1207, 1232, 1205, 1221, 1219, 1227, 
1225, 1233], vlc[21829], Web
 Content[21634], xfce4-notifyd[1347], xfce4-panel[1272], xfce4-power-man[1307, 
1325], xfce4-session[1250], xfconfd[1262], xfdesktop[1278], xfsettingsd[1274], 
xfwm4[1270]

checkrestart output:


-- 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/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages needrestart depends on:
ii  dpkg   1.19.0.4
ii  gettext-base   0.19.8.1-4
ii  libintl-perl   1.26-2
ii  libmodule-find-perl0.13-1
ii  libmodule-scandeps-perl1.24-1
ii  libproc-processtable-perl  0.53-2+b2
ii  libsort-naturally-perl 1.03-1
ii  libterm-readkey-perl   2.37-1+b2
ii  perl   5.26.1-3
ii  xz-utils   5.2.2-1.3

Versions of packages needrestart recommends:
pn  libpam-systemd | sysvinit-core  

Versions of packages needrestart suggests:
ii  libnotify-bin  0.7.7-3

-- Configuration Files:
/etc/needrestart/needrestart.conf changed:
$nrconf{sendnotify} = 0;
$nrconf{restart} = 'a';
$nrconf{ui} = 'NeedRestart::UI::stdio';
$nrconf{blacklist} = [
# ignore sudo (not a daemon)
qr(^/usr/bin/sudo(\.dpkg-new)?$),
# ignore DHCP clients
qr(^/sbin/(dhclient|dhcpcd5|pump|udhcpc)(\.dpkg-new)?$),
# ignore apt-get (Debian Bug#784237)
qr(^/usr/bin/apt-get(\.dpkg-new)?$),
];
$nrconf{override_rc} = {
# DBus
qr(^dbus) => 0,
# display managers
qr(^gdm) => 0,
qr(^kdm) => 0,
qr(^nodm) => 0,
qr(^sddm) => 0,
qr(^wdm) => 0,
qr(^xdm) => 0,
qr(^lightdm) => 0,
qr(^slim) => 0,
qr(^lxdm) => 0,
# networking stuff
qr(^network-manager) => 0,
qr(^NetworkManager) => 0,
qr(^wpa_supplicant) => 0,
qr(^openvpn) => 0,
qr(^quagga) => 0,
qr(^tinc) => 0,
# gettys
qr(^getty@.+\.service) => 0,
# systemd --user
qr(^user@\d+\.service) => 0,
# misc
qr(^zfs-fuse) => 0,
qr(^mythtv-backend) => 0,
qr(^xendomains) => 0,
qr(^lxcfs) => 0,
# workaround for broken systemd-journald
# (see also Debian Bug#771122 & #771254)
qr(^systemd-journald) => 0,
# more systemd stuff
# (see also Debian Bug#784238 & #784437)
qr(^emergency\.service$) => 0,
qr(^rescue\.service$) => 0,
# Do not restart oneshot service apt-daily, unattended-upgrades.service
# and apt-daily-upgrade.service,see #862840
qr(^apt-daily\.service$) => 0,
qr(^apt-daily-upgrade\.service$) => 0,
qr(^unattended-upgrades\.service$) => 0,
# Ignore rc-local.service, see #852864
qr(^rc-local\.service$) => 0,
# don't restart systemd-logind, see #798097
qr(^systemd-logind) => 0,
};
$nrconf{override_cont} = {
};

Bug#877274: ruby-psych: broken symlink: /usr/lib/ruby/vendor_ruby/psych.jar -> ../../../share/java/psych.jar

[Miguel Landaeta]

severity 877274 normal
thanks

On Sat, Sep 30, 2017 at 03:20:36AM +0200, Andreas Beckmann wrote:
> Package: ruby-psych
> Version: 2.2.4-6
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
> 
> Hi,
> 
> during a test with piuparts I noticed your package ships (or creates)
> a broken symlink.

Hi,

This broken symlink is not a bug.

The symlink will only be relevant to users that use ruby-psych library
in combination with jruby.

jruby explicitly depends on ruby-psych and libpsych-java.

Most ruby users in Debian currently rely on MRI (ruby2.3 and/or ruby2.5),
so the Java extension psych.jar is of no use to them.

> 
> From the attached log (scroll to the bottom...):
> 
> 0m27.6s ERROR: FAIL: Broken symlinks:
>   /usr/lib/ruby/vendor_ruby/psych.jar -> ../../../share/java/psych.jar
> 
> Is ruby-psych missing a dependency on libpsych-java?

It's not a dependency, it's only a suggestion. That's why there is a
Suggests on libpsych-java instead of a hard dependency.

I'll close this bug later unless there is another concern I'm not
noticing right now, but as I said the broken symlink should not be a
problem.

Thanks,
Miguel.

-- 
Miguel Landaeta, nomadium at debian.org
secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key.
"Faith means not wanting to know what is true." -- Nietzsche


signature.asc
Description: PGP signature

Bug#886399: RFS: opencascade/7.2.0-2 [ITP]

[kkremitzki]

Thought I'd send this along to debian-science as well.

On Fri, 05 Jan 2018 05:39:25 -0600 kkremit...@gmail.com wrote:
> Package: sponsorship-requests
> Severity: wishlist
> 
> Dear mentors,
> 
> I am looking for a sponsor for my package "opencascade"
> 
>  * Package name: opencascade
>Version : 7.2.0-2
>Upstream Author : Open CASCADE S.A.S.
>  * URL : https://www.opencascade.com
>  * License : LGPL 2.1 with OpenCASCADE exception
>Section : science
> 
> It builds those binary packages:
> 
>  libopencascade-data-exchange-7.2.0 - Open CASCADE Technology module
> for CAD data format interoperabili
>  libopencascade-data-exchange-dev - Open CASCADE Technology module
for
> CAD data format interoperabili
>  libopencascade-foundation-7.2.0 - Open CASCADE Technology module
> underlying all other OCCT classes
>  libopencascade-foundation-dev - Open CASCADE Technology module
> underlying all other OCCT classes
>  libopencascade-modeling-algorithms-7.2.0 - Open CASCADE Technology
> module containing vast range of geometric
>  libopencascade-modeling-algorithms-dev - Open CASCADE Technology
> module containing vast range of geometric
>  libopencascade-modeling-data-7.2.0 - Open CASCADE Technology data
> structures for 2D/3D geometric primi
>  libopencascade-modeling-data-dev - Open CASCADE Technology data
> structures for 2D/3D geometric primi
>  libopencascade-ocaf-7.2.0 - Open CASCADE Technology module offering
> solutions for application
>  libopencascade-ocaf-dev - Open CASCADE Technology module offering
> solutions for application
>  libopencascade-visualization-7.2.0 - Open CASCADE Technology module
> providing complex mechanisms for g
>  libopencascade-visualization-dev - Open CASCADE Technology module
> providing complex mechanisms for g
>  opencascade-draw - Open CASCADE Technology CAE test harness
>  opencascade-misc - Open CASCADE Technology CAE platform shared
library
> miscellaneous
> 
> To access further information about this package, please visit the
> following URL:
> 
> https://mentors.debian.net/package/opencascade
> 
> 
> Alternatively, one can download the package with dget using this
> command:
> 
>   dget -x https://mentors.debian.net/debian/pool/main/o/opencascade/o
pe
> ncascade_7.2.0-2.dsc
> 
> More information about opencascade can be obtained from https://www.o
pe
> ncascade.com/.
> 
> 

Bug#886401: evince: Evince does not start: Error in `evince': double free or corruption (fasttop)

[Geoffrey Ferrari]

Package: evince
Version: 3.26.0-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

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

   * What led up to the situation?
Trying to run evince from command line or from gnome desktop, without or
without a pdf file to view.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
Tried executing "evince" from command line with no pdf file specified.
   * What was the outcome of this action?

The following error message is reported:
*** Error in `evince': double free or corruption (fasttop): 0x55884b31a380
***
=== Backtrace: =
/lib/x86_64-linux-gnu/libc.so.6(+0x722fb)[0x7fe7fcdcf2fb]
/lib/x86_64-linux-gnu/libc.so.6(+0x7895e)[0x7fe7fcdd595e]
/lib/x86_64-linux-gnu/libc.so.6(+0x791be)[0x7fe7fcdd61be]
/usr/lib/x86_64-linux-
gnu/libfontconfig.so.1(FcConfigParseAndLoad+0x13a)[0x7fe7f9ccdd4a]
/usr/lib/x86_64-linux-gnu/libfontconfig.so.1(+0x2415e)[0x7fe7f9cce15e]
/lib/x86_64-linux-gnu/libexpat.so.1(+0xade8)[0x7fe7f6550de8]
/lib/x86_64-linux-gnu/libexpat.so.1(+0xbbbc)[0x7fe7f6551bbc]
/lib/x86_64-linux-gnu/libexpat.so.1(+0x9803)[0x7fe7f654f803]
/lib/x86_64-linux-gnu/libexpat.so.1(+0xa4c5)[0x7fe7f65504c5]
/lib/x86_64-linux-gnu/libexpat.so.1(XML_ParseBuffer+0x7d)[0x7fe7f655407d]
/usr/lib/x86_64-linux-gnu/libfontconfig.so.1(+0x23b43)[0x7fe7f9ccdb43]
/usr/lib/x86_64-linux-
gnu/libfontconfig.so.1(FcConfigParseAndLoad+0x366)[0x7fe7f9ccdf76]
/usr/lib/x86_64-linux-
gnu/libfontconfig.so.1(FcConfigParseAndLoad+0x3d8)[0x7fe7f9ccdfe8]
/usr/lib/x86_64-linux-gnu/libfontconfig.so.1(+0x2415e)[0x7fe7f9cce15e]
/lib/x86_64-linux-gnu/libexpat.so.1(+0xade8)[0x7fe7f6550de8]
/lib/x86_64-linux-gnu/libexpat.so.1(+0xbbbc)[0x7fe7f6551bbc]
/lib/x86_64-linux-gnu/libexpat.so.1(+0x9803)[0x7fe7f654f803]
/lib/x86_64-linux-gnu/libexpat.so.1(+0xa4c5)[0x7fe7f65504c5]
/lib/x86_64-linux-gnu/libexpat.so.1(XML_ParseBuffer+0x7d)[0x7fe7f655407d]
/usr/lib/x86_64-linux-gnu/libfontconfig.so.1(+0x23b43)[0x7fe7f9ccdb43]
/usr/lib/x86_64-linux-
gnu/libfontconfig.so.1(FcConfigParseAndLoad+0x366)[0x7fe7f9ccdf76]
/usr/lib/x86_64-linux-gnu/libfontconfig.so.1(+0x16d34)[0x7fe7f9cc0d34]
/usr/lib/x86_64-linux-gnu/libfontconfig.so.1(+0x16f86)[0x7fe7f9cc0f86]
/usr/lib/x86_64-linux-gnu/libfontconfig.so.1(+0xaa57)[0x7fe7f9cb4a57]
/usr/lib/x86_64-linux-
gnu/libfontconfig.so.1(FcConfigSubstituteWithPat+0xa15)[0x7fe7f9cb6ae5]
/usr/lib/x86_64-linux-gnu/libpangocairo-1.0.so.0(+0x9728)[0x7fe7feaf6728]
/usr/lib/x86_64-linux-gnu/libpangoft2-1.0.so.0(+0xa562)[0x7fe7f9ef9562]
/usr/lib/x86_64-linux-gnu/libpango-1.0.so.0(+0x17a67)[0x7fe7fe8b7a67]
/usr/lib/x86_64-linux-
gnu/libpango-1.0.so.0(pango_itemize_with_base_dir+0xa0)[0x7fe7fe8b90c0]
/usr/lib/x86_64-linux-gnu/libpango-1.0.so.0(+0x2175d)[0x7fe7fe8c175d]
/usr/lib/x86_64-linux-
gnu/libpango-1.0.so.0(pango_layout_get_unknown_glyphs_count+0x32)[0x7fe7fe8c2b42]
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0(+0x1a3aaa)[0x7fe7ff195aaa]
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0(+0x1a3b18)[0x7fe7ff195b18]
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0(+0x1a3c88)[0x7fe7ff195c88]
/usr/lib/x86_64-linux-
gnu/libgobject-2.0.so.0(g_type_create_instance+0x1e5)[0x7fe7fd979735]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x155d8)[0x7fe7fd95a5d8]
/usr/lib/x86_64-linux-
gnu/libgobject-2.0.so.0(g_object_new_with_properties+0x2f5)[0x7fe7fd95bd75]
/usr/lib/x86_64-linux-
gnu/libgobject-2.0.so.0(g_object_new+0xc1)[0x7fe7fd95c7f1]
evince(+0x4dd15)[0x558849189d15]
/usr/lib/x86_64-linux-
gnu/libgobject-2.0.so.0(g_type_create_instance+0x1e5)[0x7fe7fd979735]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x155d8)[0x7fe7fd95a5d8]
/usr/lib/x86_64-linux-
gnu/libgobject-2.0.so.0(g_object_new_with_properties+0x2f5)[0x7fe7fd95bd75]
/usr/lib/x86_64-linux-
gnu/libgobject-2.0.so.0(g_object_new+0xc1)[0x7fe7fd95c7f1]
evince(+0x2cfe0)[0x558849168fe0]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x15790)[0x7fe7fd95a790]
/usr/lib/x86_64-linux-
gnu/libgobject-2.0.so.0(g_object_new_valist+0x3d0)[0x7fe7fd95c450]
/usr/lib/x86_64-linux-
gnu/libgobject-2.0.so.0(g_object_new+0x99)[0x7fe7fd95c7c9]
evince(+0x2d4f2)[0x5588491694f2]
evince(+0x39ba3)[0x558849175ba3]
/usr/lib/x86_64-linux-
gnu/libgobject-2.0.so.0(g_type_create_instance+0x1e5)[0x7fe7fd979735]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x155d8)[0x7fe7fd95a5d8]
/usr/lib/x86_64-linux-
gnu/libgobject-2.0.so.0(g_object_new_valist+0x3d0)[0x7fe7fd95c450]
/usr/lib/x86_64-linux-
gnu/libgobject-2.0.so.0(g_object_new+0x99)[0x7fe7fd95c7c9]
evince(+0x3ba7b)[0x558849177a7b]
evince(+0x24015)[0x558849160015]
evince(+0x1fc44)[0x55884915bc44]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7fe7fcd7d561]
evince(+0x1fdaa)[0x55884915bdaa]
=== Memory map: 
55884913c000-5588491a3000 r-xp  08:01 1060629
/usr/bin/evince
5588493a2000-5588493a7000 r--p 00066000 08:01 1060629
/usr/bin/evince
5588493a7000-5588493a8000 rw-p 0006b000 08:01 1060629
/usr/bin/evince
55884aff-55884b32f000 

Bug#849691: RFS: gnome-shell-extension-radio/8-1 [ITP] -- GNOME shell

[leo]

5 janvier 2018 12:33 "Tobias Frost"  a écrit:

> On Fri, Jan 05, 2018 at 10:41:49AM +, l...@ndrs.fr wrote:
> 
>> Hi Tobias,
>> 
>> It's fixed now, source package is uploaded [0]. Wrong e-mail in d/changelog, 
>> so it was rejected by
>> debexpo.
>> 
>> [0]: https://mentors.debian.net/package/gnome-shell-extension-radio
> 
> Ok!
> Last thing to change:
> When bumping d/compat, you also need to update the Build-Depend: debhelper 
> (>=11)

Done.

> (Note that lintian emitted a warning on that. If you do not run linitian as 
> part of
> your build process, please consider it. Best, automate it, so that every 
> build will
> run linitian. As an example, I've intergrated it into pbuilder.)

I just didn't see it, but yes, I'm using it and it's already automated.

> Speaking of linitan, there is currently a lintian error about precompiled 
> schema files.
> This is a new one, but I currently do not have any idea how to fix that; so 
> ignore that
> at the moment..)

I saw this one too. Don't know how to fix it. But it seems to be present in 
other gnome-shell-extension packages so...

>> -- Léo

Bug#886400: python3-pyqt5.qtwebengine: segfaults on simple test

[David Bremner]

Package: python3-pyqt5.qtwebengine
Version: 5.9.2+dfsg-1
Severity: important

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

I encountered this when trying to run webmacs (a browser written in
python) on Debian.

The attached script segfaults, seemingly on any URL. Feel free to
adjust the severity up or down; I'm guessing the package works for
some people / applications, but this seems like pretty core
functionality to be broken.

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

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

Versions of packages python3-pyqt5.qtwebengine depends on:
ii  libc6   2.25-5
ii  libqt5core5a5.9.2+dfsg-6
ii  libqt5gui5  5.9.2+dfsg-6
ii  libqt5webengine55.9.2+dfsg-2
ii  libqt5webenginecore55.9.2+dfsg-2
ii  libqt5webenginewidgets5 5.9.2+dfsg-2
ii  libqt5widgets5  5.9.2+dfsg-6
ii  libstdc++6  7.2.0-18
ii  python3 3.6.4-1
ii  python3-pyqt5.qtwebchannel  5.9.2+dfsg-1

python3-pyqt5.qtwebengine recommends no packages.

python3-pyqt5.qtwebengine suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQGzBAEBCAAdFiEE3VS2dnyDRXKVCQCp8gKXHaSnniwFAlpPZAQACgkQ8gKXHaSn
niwVqAv/eS5KaAeWk9ngJUi6AXWAG0dnntZhKwyi7mYfvD6faTtjQg1ig4F93aSN
BV+45qjwJqWsOdvyrV3rOODkBYEJe2eThjGjtwFPY17+8KLaN0oW369Y4MSxmN9u
cbhQMMmFYV6Ks0X0aGfZEuUlnolor2gkbdGpsycwInC6Tyg6oauUu1v8hbd5oVnu
N0gEZx/5hEj8YbLZoUxYrV7lyw4bxpcbdk5oYTLwJbgn7GYoCwtCYrte2GzetlYr
GuoQgTL5hZMowmz5mfWmp2PirWBnwIgbMP7MG8+hjKD+dl749fWh7bnFnkfkpU+f
rlSFEtmMnRpcVMFpwDESf61W8qcMX+c7SZ/jhN+0O2g3SUdywGiD1Nfu68yxp7SR
OMqlngtiK05fpS9DkXyr/h4uLYn56RRcU/78evtqxcGr9JQoM8coNeQBpskmcUJK
f8z1YAuCDVy5ag2DpEyvBV7pinEYtKcP8dR0zZ44RL320YW1i+iifGV3kgfQm5ZI
xccf0Ilv
=ZOUB
-END PGP SIGNATURE-
#!/usr/bin/env python3
# vim: ft=python fileencoding=utf-8 sts=4 sw=4 et:

# Copyright 2014-2017 Florian Bruhin (The Compiler) 
#
# This file is part of qutebrowser.
#
# qutebrowser is free software: you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation, either version 3 of the License, or
# (at your option) any later version.
#
# qutebrowser is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with qutebrowser.  If not, see .

"""Very simple browser for testing purposes."""

import sys
import argparse

from PyQt5.QtCore import QUrl
from PyQt5.QtWidgets import QApplication
from PyQt5.QtWebEngineWidgets import QWebEngineView


def parse_args():
"""Parse commandline arguments."""
parser = argparse.ArgumentParser()
parser.add_argument('url', help='The URL to open')
return parser.parse_known_args()[0]


if __name__ == '__main__':
args = parse_args()
app = QApplication(sys.argv)
wv = QWebEngineView()

wv.loadStarted.connect(lambda: print("Loading started"))
wv.loadProgress.connect(lambda p: print("Loading progress: {}%".format(p)))
wv.loadFinished.connect(lambda: print("Loading finished"))

wv.load(QUrl.fromUserInput(args.url))
wv.show()

app.exec_()

Bug#886399: RFS: opencascade/7.2.0-2 [ITP]

[kkremitzki]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "opencascade"

 * Package name: opencascade
   Version : 7.2.0-2
   Upstream Author : Open CASCADE S.A.S.
 * URL : https://www.opencascade.com
 * License : LGPL 2.1 with OpenCASCADE exception
   Section : science

It builds those binary packages:

 libopencascade-data-exchange-7.2.0 - Open CASCADE Technology module
for CAD data format interoperabili
 libopencascade-data-exchange-dev - Open CASCADE Technology module for
CAD data format interoperabili
 libopencascade-foundation-7.2.0 - Open CASCADE Technology module
underlying all other OCCT classes
 libopencascade-foundation-dev - Open CASCADE Technology module
underlying all other OCCT classes
 libopencascade-modeling-algorithms-7.2.0 - Open CASCADE Technology
module containing vast range of geometric
 libopencascade-modeling-algorithms-dev - Open CASCADE Technology
module containing vast range of geometric
 libopencascade-modeling-data-7.2.0 - Open CASCADE Technology data
structures for 2D/3D geometric primi
 libopencascade-modeling-data-dev - Open CASCADE Technology data
structures for 2D/3D geometric primi
 libopencascade-ocaf-7.2.0 - Open CASCADE Technology module offering
solutions for application
 libopencascade-ocaf-dev - Open CASCADE Technology module offering
solutions for application
 libopencascade-visualization-7.2.0 - Open CASCADE Technology module
providing complex mechanisms for g
 libopencascade-visualization-dev - Open CASCADE Technology module
providing complex mechanisms for g
 opencascade-draw - Open CASCADE Technology CAE test harness
 opencascade-misc - Open CASCADE Technology CAE platform shared library
miscellaneous

To access further information about this package, please visit the
following URL:

https://mentors.debian.net/package/opencascade


Alternatively, one can download the package with dget using this
command:

  dget -x https://mentors.debian.net/debian/pool/main/o/opencascade/ope
ncascade_7.2.0-2.dsc

More information about opencascade can be obtained from https://www.ope
ncascade.com/.


Regards,
 Kurt Kremitzki

Bug#886342: systemd-networkd: Unknown section 'Tap'. Ignoring.

[Wolfgang Walter]

On Thursday, 4 January 2018 19:54:41 CET Michael Biebl wrote:
> Am 04.01.2018 um 19:30 schrieb Wolfgang Walter:
> > Package: systemd
> > Version: 236-2
> > 
> > Problem: since upgrading to 236-1 I get the following error:
> > 
> > systemd-networkd:[810]: /etc/systemd/network/tunnel.netdev: :5: Unknown
> > section 'Tap'. Ignoring.

I'm not familiar with the source code of systemd, but this false warnings may 
result from

network/netdev/netdev.c, line 603: netdev_load_one()

this functions calls config_parse_many() from shared/conf_parser.c.

The first time netdev_load_one() calls it (line 634) to inspect the sections 
Match and NetDev because it does not know at that point which kind of netdev 
will be defined.

In  shared/conf-parser.c config_parse_many() calls config_parse_many_files() 
=> config_parse() => parse_line().

parse_line() emits that warning in line 229 of shared/conf_parser.c when it 
parses the VLAN/MACVTAP/... section as in this first call  netdev_load_one() 
does not include them in the list of valid sections.

Maybe  netdev_load_one() should set the flag CONFIG_PARSE_RELAXED for the 
first call.


I looked at the code

https://sources.debian.org/src/systemd/236-2/src/


Regards,
-- 
Wolfgang Walter
Studentenwerk München
Anstalt des öffentlichen Rechts

Bug#886395: /usr/bin/owncloud: fails to connect to the server

[Sandro Knauß]

Forwarded: https://github.com/owncloud/client/issues/6285

Hey,

sofar this issue was only spotted with NextCloud 12. The temporally solution 
is to install the "old" owncloud-client 2.3.3 from snapshots.d.o:
deb [check-valid-until=no] http://snapshot.debian.org/archive/debian/
20170911T044212Z/ sid main

As this is not a Debian specific issue, I opened a upstream bugreport. Fell 
free to add more information at the upstream bugreport directly, if you find 
any.

hefee

--

On Freitag, 5. Januar 2018 11:50:14 CET Nicolas Évrard wrote:
> Package: owncloud-client
> Version: 2.4.0+dfsg-1
> Severity: important
> File: /usr/bin/owncloud
> 
> Dear Maintainer,
> 
> I rebooted my computer after upgrading to the newer kernel and my
> owncloud client suddenly stop connecting to my server.
> 
> When I use the logging window here are some of the network error I
> have:
> 
> QNetworkReply::NetworkError(ServiceUnavailableError) "Error transferring
> https:///remote.php/dav/files// - server replied: " QVariant(int,
> 503)
> 
> The 503 HTTP Error seems strange as I can access the web interface of
> nextcloud through firefox. When I try to reach the aforementioned URL
> with firefox I've got a message telling me that I reached a WebDAV
> interface which indicates that everything is normal.
> 
> I also have this error:
> 
> QNetworkReply::NetworkError(ServiceUnavailableError) "Error transferring
> https:///status.php - server replied: " QVariant(int, 503)
> 
> But when I use curl to fetch this page I receive the expected JSON:
> 
>
> {"installed":true,"maintenance":false,"needsDbUpgrade":false,"version":"12.
> 0.4.3","versionstring":"12.0.4","edition":"","productname":"Nextcloud"}




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

Bug#886398: cryptsetup doesn't correctly unmount encrypted disk

[Michael S]

Package: cryptsetup
Version: 2:1.7.3-4
Severity: important

Dear Maintainer,

cryptsetup on my system doesn't close properly encrypted disks on 
reboot/shutdown, reporting '(busy)' message several times until failing.

I have this problem since moved from jessie to stretch a year ago and the 
problem has not been fixed until now.

I know there is a ticket 792552 suggesting some patches but neigher is working 
for me, I have tried:
- removing /run/udev/control before do_stop() in cryptsetup.functions
- adding `dmsetup remove_all` to do_stop()

Please could you be so kind and fix the bug properly in the package existing in 
stable Debian release?

-- Package-specific info:

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

Kernel: Linux 4.9.0-5-amd64 (SMP w/4 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: sysvinit (via /sbin/init)

Versions of packages cryptsetup depends on:
ii  cryptsetup-bin 2:1.7.3-4
ii  debconf [debconf-2.0]  1.5.61
ii  dmsetup2:1.02.142-1
ii  libc6  2.24-11+deb9u1

Versions of packages cryptsetup recommends:
ii  busybox 1:1.22.0-19+b3
ii  console-setup   1.164
ii  initramfs-tools [linux-initramfs-tool]  0.130
ii  kbd 2.0.3-2+b1

Versions of packages cryptsetup suggests:
ii  dosfstools  4.1-1
pn  keyutils
ii  liblocale-gettext-perl  1.07-3+b1

-- Configuration Files:
/etc/init.d/cryptdisks changed [not included]

-- debconf information:
  cryptsetup/prerm_active_mappings: true

Bug#849691: RFS: gnome-shell-extension-radio/8-1 [ITP] -- GNOME shell

[Tobias Frost]

On Fri, Jan 05, 2018 at 10:41:49AM +, l...@ndrs.fr wrote:
> Hi Tobias,
> 
> It's fixed now, source package is uploaded [0]. Wrong e-mail in d/changelog, 
> so it was rejected by debexpo.
> 
> [0]: https://mentors.debian.net/package/gnome-shell-extension-radio

Ok! 
Last thing to change:
When bumping d/compat, you also need to update the Build-Depend: debhelper 
(>=11)

(Note that lintian emitted a warning on that. If you do not run linitian as 
part of
your build process, please consider it. Best, automate it, so that every build 
will
run linitian. As an example, I've intergrated it into pbuilder.)
 
Speaking of linitan, there is currently a lintian error about precompiled 
schema files.
This is a new one, but I currently do not have any idea how to fix that; so 
ignore that
at the moment..)

> -- Léo

Bug#884740: RFS: pokemmo/1.4.2-1 [ITP] -- Multiplayer online game based on the Pokemon universe

[Carlos Donizete Froes]

Hi Tobias,

> One thing I need to talk to you: Please do NOT modify
> already released releases. In other words: NEVER release
> different code/stuff using the same version identifier.
> This just calls for disaster, as you now have to 1.4.3 in
> the wild.
> 
> In this case the changes were even not necessary for an
> upload. But now I have to ask you to increment the upstream
> version number and then ping me again for sponsoring when ready.

I apologize for my ignorance, it was not intentional, I was worried about the 
LICENSE part of the
software. :(

This will not happen again. Thank you!

> For the Debian changes:
> Please note that the license grant must be verbose -- a word-by-word
> copx of the original text. As the license grant is including
> the name of the game, you need to update the grant.
> Basically you want the paragraph you have added on top of LICENSE.

I made the change in 'd/copyright', copying from the top of the LICENSE.
Thanks!

-- 
⢀⣴⠾⠻⢶⣦⠀ Carlos Donizete Froes [a.k.a coringao]
⣾⠁⢠⠒⠀⣿⡁ - https://wiki.debian.org/coringao
⢿⡄⠘⠷⠚⠋⠀ GPG: 4096R/B638B780
⠈⠳⣄⠀⠀⠀   2157 630B D441 A775 BEFF  D35F FA63 ADA6 B638 B780

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

Bug#883628: ITP: ioport -- direct access to I/O ports from the command line

[Tobias Frost]

On Fri, Jan 05, 2018 at 11:44:55AM +0100, Lubomir Rintel wrote:
> On Fri, 05 Jan 2018 11:20:02 +0100 Lubomir Rintel 
> wrote:
> > Thank you for your review. The updated package is available here:
> > https://mentors.debian.net/debian/pool/main/i/ioport/ioport_1.2-3.dsc
> 
> This might actually need one more spin and your help (which is greatly
> appreciated).
> 
> It's not clear to me what distribution to include in the changelog
> ("sid", "unstable", "testing" or something else?)

Use unstable.
 
> Should I be bumping the package version number for each udpate? Should
> I be adding a new changelog entry for each? Even if not
> uploaded/released?

You keep the Debian revision the same until it is sponsored.
For the 1st upload, you do not add entries to the changelog as well, it
is just "Initial Packaging (Closes: #ITP-Bug-Number).
Subsequent uploads will go more into details then, listing every change
made to the packaging. 

> Also, I've added the Vcs-* tags to the debian/control file in Git, I've
> only learned about those after I've built the package linked to above.

Yeah, See my other mail!

> Thanks,
> Lubo

I recommend to browse through the documents linked in "3. Make the package"
in https://mentors.debian.net/intro-maintainers. They will probably help you
a lot to get into the (difficult) topic of packaging.
I know its a lot to read, but it helps to know "where to look"; it is not
necessary that you memorize everything to the letter, but a rough idea where
something is explained will help. (and the knowledge will also come with
using it anyway)

> 

Bug#886397: mess-desktop-entries: Should move to main

[nyav]

Package: mess-desktop-entries
Version: 0.2-3
Severity: important

Dear Maintainer, mess-desktop-entries depend on mame which is now in 
main repository. So mess-desktop-entries can be move to main.

Bug#830303: mmc0: Unexpected interrupt 0x04000000.

[Mathieu Malaterre]

Also for reference:

$ sudo lspci -s 03:00.1 -vvx
03:00.1 SD Host controller: Broadcom Limited BCM57765/57785 SDXC/MMC
Card Reader (rev 10) (prog-if 01)
Subsystem: Broadcom Limited BCM57765/57785 SDXC/MMC Card Reader
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
SERR- 
Capabilities: [160 v1] Virtual Channel
Caps: LPEVC=0 RefClk=100ns PATEntryBits=1
Arb: Fixed- WRR32- WRR64- WRR128-
Ctrl: ArbSelect=Fixed
Status: InProgress-
VC0: Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
Arb: Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=ff
Status: NegoPending- InProgress-
Kernel driver in use: sdhci-pci
Kernel modules: sdhci_pci
00: e4 14 bc 16 06 00 10 00 10 01 05 08 40 00 80 00
10: 0c 00 82 c1 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 e4 14 bc 96
30: 00 00 00 00 48 00 00 00 00 00 00 00 0b 02 00 00

Bug#883628: ITP: ioport -- direct access to I/O ports from the command line

[Tobias Frost]

Control: tags -1 moreinfo

Hi Lubomir,

On Fri, Jan 05, 2018 at 11:20:02AM +0100, Lubomir Rintel wrote:
> Control: tags -1 - moreinfo
> 
> On Thu, 04 Jan 2018 19:13:00 +0100 Tobias Frost 
> wrote:
> > Hi,
> > 
> > here's a review:
> > - d/changelog is for UNRELEASED.
> > (- you should also update the timestamp)
>
> Changed to sid. Hope that's all right.

Usually we write "unstable".
Note that dch(1) when invoked with "-r" will do that for you,
along with updating the timestamp. (note that dch will throw away
it when you do not edit anything in the log, workaround is 'dch -r ""')

> > - Optional: Please add a VCS for the packageing. For example you can
> > use salsa.debian.org to host it.
> 
> https://salsa.debian.org/lkundrak-guest/ioport
> 
> Done.

Cool!
However, please add the appropiate VCS-* fields to d/control:
VCS-Git: https://salsa.debian.org/lkundrak-guest/ioport.git
VCS-Browser: https://salsa.debian.org/lkundrak-guest/ioport

> > - Did you try to forward the patches to upstream?
> 
> Did so now. Just emailed them privately, because there's no list or bug
> tracker.

+1
You might want to add a "Forwarded: yes, by email" to the dep-3 header of
the patches to document that.
 
> > 
> > It's a pitty that it was "UNRELEASED..." This is the only showstopper
> > in the package and the other thinfs would have been fixable in a
> later
> > releases...
> > 
> > Please iterate and then remove the moreinfo tag...
> 
> Thank you for your review. The updated package is available here:
> https://mentors.debian.net/debian/pool/main/i/ioport/ioport_1.2-3.dsc
>

One small thing: Please enable hardening. You can add this line to
the top of d/rules to do the job:

export DEB_BUILD_MAINT_OPTIONS = hardening=+all

See for details: https://wiki.debian.org/Hardening


Sorry for the addtional stuff, but I guess we're close for an upload!
Ping me when ready!

--
tobi

> Lubo
>

Bug#886396: byzanz-record doesn't honor -w

[Jörg Sommer]

Package: byzanz
Version: 0.3.0+git20160312-2
Severity: normal

Hi,

I'm having a second display attached which is why my desktop is wider than
the rectangle I would like to capture: 7680x2160 vs. 3840x2160. But using
the options -w 3840 -h 2160 -x 0 -y 0 doesn't narrow the video to the
expected screen. I still get the whole desktop recorded.

The whole command line: byzanz-record -c -d 5 -w 3840 -h 2160 -x 0 -y 0 
video.ogv

Bye Jörg

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

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

Versions of packages byzanz depends on:
ii  gstreamer1.0-libav  1.12.4-1
ii  gstreamer1.0-plugins-base   1.12.4-1
ii  gstreamer1.0-plugins-good   1.12.4-1
ii  libc6   2.26-1
ii  libcairo2   1.15.8-3
ii  libglib2.0-02.54.2-5
ii  libgstreamer-plugins-base1.0-0  1.12.4-1
ii  libgstreamer1.0-0   1.12.4-1
ii  libgtk-3-0  3.22.26-2
ii  libxdamage1 1:1.1.4-3
ii  libxfixes3  1:5.0.3-1

byzanz recommends no packages.

byzanz suggests no packages.

-- no debconf information


signature.asc
Description: PGP signature

Bug#830303: mmc0: Unexpected interrupt 0x04000000.

[Mathieu Malaterre]

Control: found -1 4.14+88~bpo9+1

Same here, using a MacBookPro10,1. I cannot get the driver to work
when SDHC Samsung Evo 16GB is placed in card reader (bug is totally
reproducible). If I remove the card and place it in a USB reader
(USB-HUB reader) then everything is fine. I even tested using f3probe:

https://packages.qa.debian.org/f/f3.html

The card only work when placed in USB-HUB reader.

For reference:

[  220.210842] mmc0: Tuning timeout, falling back to fixed sampling clock
[  220.210934] mmc0: new ultra high speed DDR50 SDHC card at address 59b4
[  220.219075] mmcblk0: mmc0:59b4 0 14.9 GiB
[  230.362858] mmc0: Timeout waiting for hardware interrupt.
[  230.362868] mmc0: sdhci:  SDHCI REGISTER DUMP ===
[  230.362918] mmc0: sdhci: Sys addr:  0x00c8 | Version:  0x1502
[  230.362927] mmc0: sdhci: Blk size:  0x7200 | Blk cnt:  0x0008
[  230.362937] mmc0: sdhci: Argument:  0x | Trn mode: 0x003b
[  230.362946] mmc0: sdhci: Present:   0x1fff | Host ctl: 0x001f
[  230.362955] mmc0: sdhci: Power: 0x000f | Blk gap:  0x
[  230.362964] mmc0: sdhci: Wake-up:   0x | Clock:0x0007
[  230.362974] mmc0: sdhci: Timeout:   0x000a | Int stat: 0x
[  230.362982] mmc0: sdhci: Int enab:  0x02ff008b | Sig enab: 0x02ff008b
[  230.362992] mmc0: sdhci: AC12 err:  0x0010 | Slot int: 0x
[  230.363001] mmc0: sdhci: Caps:  0x176ec8b0 | Caps_1:   0x03002177
[  230.363011] mmc0: sdhci: Cmd:   0x123a | Max curr: 0x
[  230.363020] mmc0: sdhci: Resp[0]:   0x1201 | Resp[1]:  0x
[  230.363029] mmc0: sdhci: Resp[2]:   0x | Resp[3]:  0x
[  230.363035] mmc0: sdhci: Host ctl2: 0x804c
[  230.363047] mmc0: sdhci: ADMA Err:  0x0001 | ADMA Ptr: 0x000457940204
[  230.363049] mmc0: sdhci: 
[  230.363119] mmc0: Unexpected interrupt 0x0400.
[  230.363128] mmc0: sdhci:  SDHCI REGISTER DUMP ===
[  230.363157] mmc0: sdhci: Sys addr:  0x | Version:  0x1502
[  230.363166] mmc0: sdhci: Blk size:  0x7200 | Blk cnt:  0x0008
[  230.363174] mmc0: sdhci: Argument:  0x | Trn mode: 0x0033
[  230.363184] mmc0: sdhci: Present:   0x1fff0001 | Host ctl: 0x001f
[  230.363193] mmc0: sdhci: Power: 0x000f | Blk gap:  0x
[  230.363203] mmc0: sdhci: Wake-up:   0x | Clock:0x0007
[  230.363214] mmc0: sdhci: Timeout:   0x000a | Int stat: 0x
[  230.363225] mmc0: sdhci: Int enab:  0x02ff008b | Sig enab: 0x02ff008b
[  230.363234] mmc0: sdhci: AC12 err:  0x | Slot int: 0x
[  230.363244] mmc0: sdhci: Caps:  0x176ec8b0 | Caps_1:   0x03002177
[  230.363253] mmc0: sdhci: Cmd:   0x0c1a | Max curr: 0x
[  230.363263] mmc0: sdhci: Resp[0]:   0x1201 | Resp[1]:  0x
[  230.363272] mmc0: sdhci: Resp[2]:   0x | Resp[3]:  0x
[  230.363278] mmc0: sdhci: Host ctl2: 0x800c
[  230.363292] mmc0: sdhci: ADMA Err:  0x0001 | ADMA Ptr: 0x000457940204
[  230.363294] mmc0: sdhci: 
[  230.363509] mmcblk0: error -110 sending stop command, original cmd
response 0x0, card status 0x400900
[  230.418897] mmc0: Tuning timeout, falling back to fixed sampling clock
[  240.602915] mmc0: Timeout waiting for hardware interrupt.
[  240.602924] mmc0: sdhci:  SDHCI REGISTER DUMP ===
[  240.602971] mmc0: sdhci: Sys addr:  0x00c8 | Version:  0x1502
[  240.602981] mmc0: sdhci: Blk size:  0x7200 | Blk cnt:  0x0008
[  240.602989] mmc0: sdhci: Argument:  0x | Trn mode: 0x003b
[  240.602999] mmc0: sdhci: Present:   0x1fff | Host ctl: 0x001f
[  240.603008] mmc0: sdhci: Power: 0x000f | Blk gap:  0x
[  240.603018] mmc0: sdhci: Wake-up:   0x | Clock:0x0007
[  240.603027] mmc0: sdhci: Timeout:   0x000a | Int stat: 0x
[  240.603036] mmc0: sdhci: Int enab:  0x02ff008b | Sig enab: 0x02ff008b
[  240.603045] mmc0: sdhci: AC12 err:  0x0010 | Slot int: 0x
[  240.603054] mmc0: sdhci: Caps:  0x176ec8b0 | Caps_1:   0x03002177
[  240.603063] mmc0: sdhci: Cmd:   0x123a | Max curr: 0x
[  240.603073] mmc0: sdhci: Resp[0]:   0x1201 | Resp[1]:  0x
[  240.603082] mmc0: sdhci: Resp[2]:   0x | Resp[3]:  0x1000
[  240.603088] mmc0: sdhci: Host ctl2: 0x804c
[  240.603100] mmc0: sdhci: ADMA Err:  0x0001 | ADMA Ptr: 0x000457940204
[  240.603102] mmc0: sdhci: 
[  240.603162] mmc0: Unexpected interrupt 0x0400.
[  240.603164] mmc0: sdhci:  SDHCI REGISTER DUMP ===
[  240.603172] mmc0: sdhci: Sys addr:  0x | Version:  0x1502
[  240.603182] mmc0: sdhci: Blk size:  0x7200 | Blk cnt:  0x0008
[  240.603192] mmc0: sdhci: Argument:  0x | Trn mode: 0x0033
[  

Bug#886328: live-boot: Please use /run/live instead of /lib/live/mount

[intrigeri]

Hi,

Benjamin Drung:
> Therefore move /lib/live/mount to /run/live and skip the intermedia
> /live mount points. This reduces code and complexity.

As someone who had to repeatedly bang his head against exactly this
part of the live-boot code (last time earlier this week), I can only
agree with the proposed simplification idea. I didn't do a full code
review though.

Cheers,
-- 
intrigeri

Bug#886395: /usr/bin/owncloud: fails to connect to the server

[Nicolas Évrard]

Package: owncloud-client
Version: 2.4.0+dfsg-1
Severity: important
File: /usr/bin/owncloud

Dear Maintainer,

I rebooted my computer after upgrading to the newer kernel and my
owncloud client suddenly stop connecting to my server.

When I use the logging window here are some of the network error I
have:

QNetworkReply::NetworkError(ServiceUnavailableError) "Error transferring 
https:///remote.php/dav/files// - server replied: " QVariant(int, 503)

The 503 HTTP Error seems strange as I can access the web interface of
nextcloud through firefox. When I try to reach the aforementioned URL
with firefox I've got a message telling me that I reached a WebDAV
interface which indicates that everything is normal.

I also have this error:

QNetworkReply::NetworkError(ServiceUnavailableError) "Error transferring 
https:///status.php - server replied: " QVariant(int, 503)

But when I use curl to fetch this page I receive the expected JSON:


{"installed":true,"maintenance":false,"needsDbUpgrade":false,"version":"12.0.4.3","versionstring":"12.0.4","edition":"","productname":"Nextcloud"}


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

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

Versions of packages owncloud-client depends on:
ii  libc6 2.26-1
ii  libgcc1   1:7.2.0-18
ii  libowncloudsync0  2.4.0+dfsg-1
ii  libqt5core5a  5.9.2+dfsg-6
ii  libqt5dbus5   5.9.2+dfsg-6
ii  libqt5gui55.9.2+dfsg-6
ii  libqt5keychain1   0.7.0-3
ii  libqt5network55.9.2+dfsg-6
ii  libqt5sql5-sqlite 5.9.2+dfsg-6
ii  libqt5webkit5 5.212.0~alpha2-5
ii  libqt5widgets55.9.2+dfsg-6
ii  libqt5xml55.9.2+dfsg-6
ii  libstdc++67.2.0-18
ii  owncloud-client-l10n  2.4.0+dfsg-1

Versions of packages owncloud-client recommends:
ii  owncloud-client-doc  2.4.0+dfsg-1

owncloud-client suggests no packages.

-- no debconf information

Bug#886356: transition: ilmbase

[Emilio Pozuelo Monfort]

Control: tags -1 confirmed

On 04/01/18 21:36, Matteo F. Vescovi wrote:
> 
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
> 
> Dear Release Team,
> 
> I'm filing this bug report for a new transition of ilmbase package.
> 
> On December 30, 2017 a testing-purpose package has been uploaded to
> experimental and it was tested building all its 25 reverse dependencies
> on the Deb-o-Matic infrastructure on amd64 architecture.

Go ahead.

Emilio

Bug#886394: java.lang.ClassNotFoundException: javafx.scene.layout.HBox

[Ludovic CHEVALIER]

Package: pdfsam
Version: 3.3.5-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I can't launch pdfsam. Here is the traceback:

Exception in thread "main" java.lang.NoClassDefFoundError: 
javafx/scene/layout/HBox
at java.base/java.lang.ClassLoader.defineClass1(Native Method)
at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1007)
at 
java.base/java.security.SecureClassLoader.defineClass(SecureClassLoader.java:174)
at 
java.base/jdk.internal.loader.BuiltinClassLoader.defineClass(BuiltinClassLoader.java:801)
at 
java.base/jdk.internal.loader.BuiltinClassLoader.findClassOnClassPathOrNull(BuiltinClassLoader.java:699)
at 
java.base/jdk.internal.loader.BuiltinClassLoader.loadClassOrNull(BuiltinClassLoader.java:622)
at 
java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:580)
at 
java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:185)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:496)
at org.pdfsam.community.App.main(App.java:34)
Caused by: java.lang.ClassNotFoundException: javafx.scene.layout.HBox
at 
java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:582)
at 
java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:185)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:496)
... 10 more

Thanks.

Ludo

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing'), (200, 'unstable'), (150, 'stable'), (100, 
'experimental')
Architecture: i386 (i686)

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

Versions of packages pdfsam depends on:
ii  libatinject-jsr330-api-java1.0+ds1-5
ii  libbcmail-java 1.58-1
ii  libbcprov-java 1.58-1
ii  libcommons-io-java 2.5-2
ii  libcommons-lang3-java  3.5-1
ii  libfontawesomefx-java  8.9-1
ii  libgettext-commons-java0.9.6-6
ii  libhibernate-validator-java4.3.3-3
ii  libjackson2-jr-java2.9.1-1
ii  liblogback-java1:1.2.3-2
ii  libsambox-java 1.1.19-1
ii  libsejda-eventstudio-java  1.0.6-1
ii  libsejda-injector-java 1.0.2-1
ii  libsejda-java  3.2.38-1
ii  libslf4j-java  1.7.25-2
ii  openjdk-8-jre [java8-runtime]  8u151-b12-1
ii  openjdk-9-jre [java8-runtime]  9.0.1+11-1
ii  openjfx8u141-b14-3

pdfsam recommends no packages.

pdfsam suggests no packages.

-- no debconf information

Bug#885649: transition: src:qscintilla2

[Emilio Pozuelo Monfort]

On 04/01/18 19:36, Scott Kitterman wrote:
> Everything that can be NMUed or binNMUed has been completed.
> 
> Ovito is a problem.  See #886340.  I've fooled around with it a bit and can't 
> get it to build, so I'll leave it for someone else.  I guess it could be 
> temporarily removed from testing to get the transition finished if the 
> maintainer doesn't turn anything up?

That's an option. Let's wait for things to age and see if they can migrate on
their own without further action.

Cheers,
Emilio

Bug#886232: perl: Sys::Syslog is not tread-safe (can segfault)

[Dominic Hargreaves]

On Wed, Jan 03, 2018 at 11:52:02AM +0100, Zdenek Salvet wrote:
> Sys::Syslog module is not thread-safe, reopening syslog connection
> (could be internal/automatic after transient transport error, without user 
> calling openlog/closelog) can crash multithreaded process 
> (Apache event MPM with mod_perl in my case).
> You can find upstream bug report at 
> https://rt.perl.org/Public/Bug/Display.html?id=132679 ,
> attached patch (serializing access to shared variable with straightforward 
> locking)
> has been tested on jessie.

Hello,

Are you able to tell whether this affects Debian stretch too?
Or at the very least please could you provide reproducing instructions?
If it's still an issue in current releases of perl we should fix it
there first/also.

By the way, you probably want to file that upstream issue on CPAN RT
rather than rt.perl.org since Sys-Syslog is not maintained by the perl5
porters - and against a current release:

https://rt.cpan.org//Dist/Display.html?Queue=Sys-Syslog

You might find it helpful for testing purposes to install the current
Sys-Syslog from CPAN locally to verify the problem with the newest
version of Sys-Syslog.

Cheers,
Dominic.

Bug#886354: transition: ros-bond-core

[Emilio Pozuelo Monfort]

Control: tags -1 confirmed

On 04/01/18 21:24, Jochen Sprickerhof wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
> 
> Dear release team,
> 
> I would like to transition ros-bond-core to unstable. I tested the
> reverse dependencies and found no problems.

Ack.

Emilio

Bug#886319: transition: ntl

[Emilio Pozuelo Monfort]

Control: tags -1 confirmed

On 04/01/18 12:52, Ximin Luo wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
> 
> ntl 10.5.0 is in experimental and ready to start the transition from 9.9.3 in 
> unstable.
> 
> I've rebuilt the relevant reverse-build-dependencies from unstable. All
> rebuilds succeed without issue:
> 
>  eclib
>  flint
>  giac
>  linbox
>  singular
>  pynac
>  flint-arb
>  sagemath
> 
> Therefore, no extra bugs need to be filed and the transition can start
> immediately or as soon as possible.
> 
> ntl is currently building in experimental but after that is done the
> auto-transition page should appear here:
> 
> https://release.debian.org/transitions/html/auto-ntl.html

Go ahead.

Emilio

Bug#886182: transition: glibc 2.26

[Emilio Pozuelo Monfort]

Control: forwarded -1 
https://release.debian.org/transitions/html/glibc-2.26.html

On 04/01/18 21:56, Aurelien Jarno wrote:
> On 2018-01-02 22:47, Emilio Pozuelo Monfort wrote:
>> Control: tags -1 confirmed
>>
>> On 02/01/18 22:37, Aurelien Jarno wrote:
>>> Package: release.debian.org
>>> Severity: normal
>>> User: release.debian@packages.debian.org
>>> Usertags: transition
>>>
>>> Dear release team,
>>>
>>> I would like to get a transition slot for glibc 2.26. It is available in
>>> experimental for one month and a half, and there is no known regression.
>>> It has been built successfully on all release architectures, and most
>>> other architectures besides kfreebsd-* which do not have build daemons
>>> anymore. The failures on hurd-i386 and hppa are being worked on and can
>>> be fixed in the upload to sid or later, so I don't think we should block
>>> the transition on that.
>>>
>>> As the glibc is using symbol versioning, there is no soname change. That
>>> said a few packages are using libc internal symbols and have to be
>>> rebuilt for this transition:
>>>  - apitrace
>>>  - bro
>>>  - dante
>>>  - libnih
>>>  - libnss-db
>>>  - p11-kit
>>>  - unscd
>>>
>>> Here is the corresponding ben file:
>>>   title = "glibc";
>>>   is_affected = .depends ~ /libc[0-9.]* \(<>>   is_good = .depends ~ /libc[0-9.]* \(<< 2.27\)/;
>>>   is_bad = .depends ~ /libc[0-9.]* \(<< 2.26\)/;
>>>
>>> In addition a few new symbols have been added that might prevent a few
>>> other packages to migrate to testing until glibc migrates if they pick
>>> up the new symbols. That's mostly the case for libm.so, which added
>>> 128-bit floating point support on amd64, i386, and ppc64el. On the
>>> libc.so side the new functions are reallocarray, preadv2 and pwritev2,
>>> which should not be widely used so far.
>>>
>>> Thanks for considering
>>
>> Please go ahead.
> 
> Thanks. I uploaded it yesterday and it has now been built on all
> official architectures.

binNMUs scheduled.

Emilio

Bug#883627: RFS: network-manager-fortisslvpn/1.2.6-1 [ITP] -- NetworkManager Fortinet SSLVPN plugin

[Lubomir Rintel]

On Tue, 02 Jan 2018 18:01:00 +0100 Lubomir Rintel 
wrote:
> Download the package with dget using this command:

An updated version:

dget -x 
https://mentors.debian.net/debian/pool/main/n/network-manager-fortisslvpn/network-manager-fortisslvpn_1.2.6-2.dsc

Bug#883628: ITP: ioport -- direct access to I/O ports from the command line

[Lubomir Rintel]

On Fri, 05 Jan 2018 11:20:02 +0100 Lubomir Rintel 
wrote:
> Thank you for your review. The updated package is available here:
> https://mentors.debian.net/debian/pool/main/i/ioport/ioport_1.2-3.dsc

This might actually need one more spin and your help (which is greatly
appreciated).

It's not clear to me what distribution to include in the changelog
("sid", "unstable", "testing" or something else?)

Should I be bumping the package version number for each udpate? Should
I be adding a new changelog entry for each? Even if not
uploaded/released?

Also, I've added the Vcs-* tags to the debian/control file in Git, I've
only learned about those after I've built the package linked to above.

Thanks,
Lubo

Bug#886393: doesn't clean up inherited children

[Wouter Verhelst]

Package: awesome
Version: 4.2-4
Severity: normal

Hi,

Part of my ~.xsession looks like this:

traystuff &
confsynaptics
setxkbmap -option compose:menu be
light-locker &
/usr/share/xscreensaver/xscreensaver-wrapper.sh -nosplash &
exec awesome

The last line means awesome now inherits the processes that were started
in the background. Unfortunately, the result is that awesome does not
appear to reap the zombies:

wouter2375  0.2  0.4 550072 72876 ?Ssl  11:04   0:05  \_ awesome
wouter2465  0.0  0.0  11096  2212 ?Ss   11:04   0:00  \_ 
/usr/bin/ssh-agent /usr/bin/im-launch /bin/bash /home/wouter/.xsession
wouter   10348  0.0  0.0  28936  4880 ?S11:34   0:00  |   
\_ /usr/lib/openssh/ssh-pkcs11-helper
wouter2555  0.0  0.0  0 0 ?Z11:04   0:00  \_ 
[traystuff] 
wouter2568  0.0  0.0  0 0 ?Z11:04   0:00  \_ 
[bash] 
wouter2569  0.0  0.0  0 0 ?Z11:04   0:00  \_ 
[xscreensaver] 

This does not appear to be proper.

If you need further information, do ask.

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

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

Versions of packages awesome depends on:
ii  dbus-user-session [default-dbus-session-bus]  1.12.2-1
ii  dbus-x11 [dbus-session-bus]   1.12.2-1
ii  gir1.2-freedesktop1.54.1-4
ii  gir1.2-pango-1.0  1.40.14-1
ii  libc6 2.26-1
ii  libcairo-gobject2 1.15.8-3
ii  libcairo2 1.15.8-3
ii  libdbus-1-3   1.12.2-1
ii  libgdk-pixbuf2.0-02.36.11-1
ii  libglib2.0-0  2.54.2-5
ii  liblua5.3-0   5.3.3-1
ii  libstartup-notification0  0.12-5
ii  libx11-6  2:1.6.4-3
ii  libxcb-cursor00.1.1-4
ii  libxcb-icccm4 0.4.1-1+b1
ii  libxcb-keysyms1   0.4.0-1+b2
ii  libxcb-randr0 1.12-1
ii  libxcb-render01.12-1
ii  libxcb-shape0 1.12-1
ii  libxcb-util0  0.3.8-3+b2
ii  libxcb-xinerama0  1.12-1
ii  libxcb-xkb1   1.12-1
ii  libxcb-xrm0   1.0-3
ii  libxcb-xtest0 1.12-1
ii  libxcb1   1.12-1
ii  libxdg-basedir1   1.2.0-1
ii  libxkbcommon-x11-00.7.1-2
ii  libxkbcommon0 0.7.1-2
ii  lua-lgi   0.9.2-1
it  menu  2.1.47+b1

Versions of packages awesome recommends:
ii  awesome-extra  2017110501
ii  feh2.22.2-1
ii  rlwrap 0.42-3
ii  x11-xserver-utils  7.7+7+b1

Versions of packages awesome suggests:
pn  awesome-doc  

-- no debconf information

Bug#866973: cyrus-imapd 3.0 needs to be (eventually) packaged

[Ondřej Surý]

Yes, the maintainer is active.

I started cyrus-imapd 3.0 packaging while ago and it's noticeable amount of 
work, so if anybody else want to join the packaging team and do the 
heavylifting before a bigger time window of free time opens for me, they would 
be welcome.

I would be happy to convert the cyrus-imapd packaging to salsa.debian.org, so 
it's easier for external contributors to add code.

O.
-- 
Ondřej Surý 

On Mon, Jan 1, 2018, at 20:36, Berhardt Eckl wrote:
> Does anybody know if maintainer is still active on this package? Is 
> there any reason why updates are not packaged?
> 
> Thx
> ___
> Pkg-Cyrus-imapd-Debian-devel mailing list
> pkg-cyrus-imapd-debian-de...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-cyrus-imapd-debian-devel

Bug#849691: RFS: gnome-shell-extension-radio/8-1 [ITP] -- GNOME shell

[leo]

Hi Tobias,

It's fixed now, source package is uploaded [0]. Wrong e-mail in d/changelog, so 
it was rejected by debexpo.

[0]: https://mentors.debian.net/package/gnome-shell-extension-radio

-- Léo

Bug#880407: #880407 xterm: font issue with FreeType 2.8; should not use the rounded ascender and descender

[Thomas Dickey]

On Fri, Jan 05, 2018 at 10:26:11AM +0100, Vincent Lefevre wrote:
> On 2018-01-05 04:13:56 -0500, Thomas Dickey wrote:
> > - Original Message -
> > | On 2018-01-05 03:59:42 -0500, Thomas Dickey wrote:
> > | > Then you should provide more information allowing this to be
> > | > reproduced.
> > | 
> > | I can reproduce this with the default config and:
> > | 
> > |   xterm -fa Monospace -fs 10 -xrm "Xft.dpi: 132"
> > | 
> > | (the "Xft.dpi: 132" is important).
> > 
> > I did that (and other values of ".dpi") without seeing any other effect than
> > the one for which I made a workaround: detecting the improper rounding and
> > forcing xterm's internal line-drawing in that case.  The line-drawing glyphs
> > were effectively shorter than some of the other characters.
> 
> Sorry, I don't understand what you mean. Can you reproduce the problem
> with that?

only for the case that I made xterm detect/workaround.

I added debug-tracing in fontutils.c to show the actual data for the
FT_Size_Metrics, as well as loading the glyph to see the pixels.
It wasn't a "black" line but rather two raster lines with low values.

The rounding change altered the weights from about 12/16 down to 8/16
or 9/16.

I added logic to add the weights and turn on xterm's line-drawing when
it fell below the threshold.

(The trace adds a lot of data; I'd turn it on by the configure with
--enable-trace, as well as editing fontutil.c to define OPT_TRACE as 2, and
defining DEBUG_XFT).

I ran that against all of the fonts from fc-list (several hundred...), found
some unrelated issues (lack of error-checking in FT_Load_Char, requiring yet
another workaround), but no more than that.

In tracing the FT_Size_Metrics, I found no font metrics which Xft could have
repaired:  all of the damage was done by the change to FreeType2.

In particular, tracing the sizes as floating point, none of the values
had nonzero fractional parts.  As far as I can see, Xft simply gets
the result from FreeType2, which has already been rounded.

-- 
Thomas E. Dickey 
https://invisible-island.net
ftp://ftp.invisible-island.net


signature.asc
Description: Digital signature

Bug#883628: ITP: ioport -- direct access to I/O ports from the command line

[Lubomir Rintel]

Control: tags -1 - moreinfo

On Thu, 04 Jan 2018 19:13:00 +0100 Tobias Frost 
wrote:
> Hi,
> 
> here's a review:
> - d/changelog is for UNRELEASED.
> (- you should also update the timestamp)

Changed to sid. Hope that's all right.

> - d/compat can be bumped to 11 (you B-D on debhelper >11 already)

Done.

> - Optional: Please add a VCS for the packageing. For example you can
> use salsa.debian.org to host it.

https://salsa.debian.org/lkundrak-guest/ioport

Done.

> - Did you try to forward the patches to upstream?

Did so now. Just emailed them privately, because there's no list or bug
tracker.

> 
> It's a pitty that it was "UNRELEASED..." This is the only showstopper
> in the package and the other thinfs would have been fixable in a
later
> releases...
> 
> Please iterate and then remove the moreinfo tag...

Thank you for your review. The updated package is available here:
https://mentors.debian.net/debian/pool/main/i/ioport/ioport_1.2-3.dsc

Lubo

Bug#674597: Please her hurry they starting to multiply

[Jonnie Brown]

You need to bring out the big guns

Bug#886392: hedgewars: Minimize build dependencies instead of depending on all of fpc

[Graham Inggs]

Source: hedgewars
Version: 0.9.23-dfsg-1
Severity: wishlist

Hi Maintainers

Installing the build dependency fpc takes up about 400MB of disk space 
and pulls in fp-docs and fpc-source.  Minimizing this to only the 
packages required:

fp-compiler
fp-units-misc
fp-units-gfx
...only takes up around 50MB of space.
I have recently made similar changes to doublecmd and ddrescueview.

You will also need to adjust the check in debian/rules when setting 
BUILD_ENGINE_C.  Instead of checking whether package fpc is installed, 
maybe just check for the existence of /usr/bin/fpc ?


However, looking at hedgewars' build logs, it appears that it FTBFS 
everywhere without a Pascal compiler anyway, so maybe just always depend 
on the Pascal dependencies and always set BUILD_ENGINE_C := NO .


Regards
Graham

Bug#866503: webkit2gtk: stuttering audio playback

[Alberto Garcia]

Control: tags -1 moreinfo

> > I just got an upgrade to surf-2.0 in Debian testing. I use surf
> > for this site:
> > 
> > http://radio.dos.nl/
> > 
> > But on several computers the sound is interrupted a few times
> > per second (I think depending on the bitrate). Downgrading to
> > 0.7 resolves the problem. Can you try this site to see if you
> > encounter the same issues?
> 
> Thank you for testing surf and providing feedback.
> 
> I can reproduce the issue you described. On the site you mentioned
> the sound is also stuttering for me (1-2 times per second), though
> it works fine on other sites like YouTube.

I can't reproduce this problem anymore (I'm using webkit2gtk 2.18.4).
Does it still happen to you?

Berto

Bug#886391: libhpipp.so: undefined symbols: needs -lcups

[Paul Wise]

Package: libhpmud0
Version: 3.17.10+repack0-2
Severity: minor
File: /usr/lib/x86_64-linux-gnu/libhpipp.so.0.0.1
User: debian...@lists.debian.org
Usertags: undefined-symbol adequate

libhpipp.so needs to link with -lcups, see the output of adequate,
symtree and objdump 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 I'm not sure if there are any
programs using the hpipp lib or if they already use the libcups symbols and 
link with the -lcups flag or not.

This bug report brought to you by adequate:

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

$ adequate libhpmud0
libhpmud0:amd64: undefined-symbol /usr/lib/x86_64-linux-gnu/libhpipp.so.0.0.1 
=> cupsLangEncoding
libhpmud0:amd64: undefined-symbol /usr/lib/x86_64-linux-gnu/libhpipp.so.0.0.1 
=> ippDelete
libhpmud0:amd64: undefined-symbol /usr/lib/x86_64-linux-gnu/libhpipp.so.0.0.1 
=> ippFirstAttribute
libhpmud0:amd64: undefined-symbol /usr/lib/x86_64-linux-gnu/libhpipp.so.0.0.1 
=> cupsSetUser
libhpmud0:amd64: undefined-symbol /usr/lib/x86_64-linux-gnu/libhpipp.so.0.0.1 
=> ippGetInteger
libhpmud0:amd64: undefined-symbol /usr/lib/x86_64-linux-gnu/libhpipp.so.0.0.1 
=> ippNew
libhpmud0:amd64: undefined-symbol /usr/lib/x86_64-linux-gnu/libhpipp.so.0.0.1 
=> ippGetBoolean
libhpmud0:amd64: undefined-symbol /usr/lib/x86_64-linux-gnu/libhpipp.so.0.0.1 
=> ippReadIO
libhpmud0:amd64: undefined-symbol /usr/lib/x86_64-linux-gnu/libhpipp.so.0.0.1 
=> cupsServer
libhpmud0:amd64: undefined-symbol /usr/lib/x86_64-linux-gnu/libhpipp.so.0.0.1 
=> ippGetValueTag
libhpmud0:amd64: undefined-symbol /usr/lib/x86_64-linux-gnu/libhpipp.so.0.0.1 
=> cupsLastError
libhpmud0:amd64: undefined-symbol /usr/lib/x86_64-linux-gnu/libhpipp.so.0.0.1 
=> ippSetVersion
libhpmud0:amd64: undefined-symbol /usr/lib/x86_64-linux-gnu/libhpipp.so.0.0.1 
=> ippGetName
libhpmud0:amd64: undefined-symbol /usr/lib/x86_64-linux-gnu/libhpipp.so.0.0.1 
=> cupsLangDefault
libhpmud0:amd64: undefined-symbol /usr/lib/x86_64-linux-gnu/libhpipp.so.0.0.1 
=> ippGetString
libhpmud0:amd64: undefined-symbol /usr/lib/x86_64-linux-gnu/libhpipp.so.0.0.1 
=> httpConnectEncrypt
libhpmud0:amd64: undefined-symbol /usr/lib/x86_64-linux-gnu/libhpipp.so.0.0.1 
=> ippSetOperation
libhpmud0:amd64: undefined-symbol /usr/lib/x86_64-linux-gnu/libhpipp.so.0.0.1 
=> ippAddBoolean
libhpmud0:amd64: undefined-symbol /usr/lib/x86_64-linux-gnu/libhpipp.so.0.0.1 
=> cupsDoRequest
libhpmud0:amd64: undefined-symbol /usr/lib/x86_64-linux-gnu/libhpipp.so.0.0.1 
=> cupsDoFileRequest
libhpmud0:amd64: undefined-symbol /usr/lib/x86_64-linux-gnu/libhpipp.so.0.0.1 
=> ippAddInteger
libhpmud0:amd64: undefined-symbol /usr/lib/x86_64-linux-gnu/libhpipp.so.0.0.1 
=> ippSetRequestId
libhpmud0:amd64: undefined-symbol /usr/lib/x86_64-linux-gnu/libhpipp.so.0.0.1 
=> ippGetGroupTag
libhpmud0:amd64: undefined-symbol /usr/lib/x86_64-linux-gnu/libhpipp.so.0.0.1 
=> ippGetStatusCode
libhpmud0:amd64: undefined-symbol /usr/lib/x86_64-linux-gnu/libhpipp.so.0.0.1 
=> ippPort
libhpmud0:amd64: undefined-symbol /usr/lib/x86_64-linux-gnu/libhpipp.so.0.0.1 
=> cupsEncryption
libhpmud0:amd64: undefined-symbol /usr/lib/x86_64-linux-gnu/libhpipp.so.0.0.1 
=> ippNextAttribute
libhpmud0:amd64: undefined-symbol /usr/lib/x86_64-linux-gnu/libhpipp.so.0.0.1 
=> cupsUser
libhpmud0:amd64: undefined-symbol /usr/lib/x86_64-linux-gnu/libhpipp.so.0.0.1 
=> ippNewRequest
libhpmud0:amd64: undefined-symbol /usr/lib/x86_64-linux-gnu/libhpipp.so.0.0.1 
=> ippErrorString
libhpmud0:amd64: undefined-symbol /usr/lib/x86_64-linux-gnu/libhpipp.so.0.0.1 
=> ippAddStrings
libhpmud0:amd64: undefined-symbol /usr/lib/x86_64-linux-gnu/libhpipp.so.0.0.1 
=> ippAddString
libhpmud0:amd64: undefined-symbol /usr/lib/x86_64-linux-gnu/libhpipp.so.0.0.1 
=> ippWriteIO
libhpmud0:amd64: undefined-symbol /usr/lib/x86_64-linux-gnu/libhpipp.so.0.0.1 
=> httpClose

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

$ lddtree /usr/lib/x86_64-linux-gnu/libhpipp.so.0.0.1
libhpipp.so.0.0.1 => /usr/lib/x86_64-linux-gnu/libhpipp.so.0.0.1 (interpreter 
=> none)
libhpmud.so.0 => /usr/lib/x86_64-linux-gnu/libhpmud.so.0
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
ld-linux-x86-64.so.2 => /lib/x86_64-linux-gnu/ld-linux-x86-64.so.2
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2
libusb-1.0.so.0 => /lib/x86_64-linux-gnu/libusb-1.0.so.0
libudev.so.1 => /lib/x86_64-linux-gnu/libudev.so.1
libnetsnmp.so.30 => 

Bug#674597: Info received ()

[Jonnie Brown]

These web bugs are eating me alive help me

On Jan 3, 2018 4:08 PM, "Jonnie Brown"  wrote:


On Jan 3, 2018 4:06 PM, "Debian Bug Tracking System" 
wrote:

> Thank you for the additional information you have supplied regarding
> this Bug report.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> Your message has been sent to the package maintainer(s):
>  Debian Games Team 
>
> If you wish to submit further information on this problem, please
> send it to 674...@bugs.debian.org.
>
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 674597: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674597
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>

Bug#886390: debian-ports-archive-keyring: obsolete conffile left behind

[Sven Joachim]

Package: debian-ports-archive-keyring
Version: 2017.12.30
Severity: normal

Upgrading from 2016.11.28 left the obsolete conffile
/etc/apt/trusted.gpg.d/debian-ports-archive-2016.gpg on my system.  It
seems you forgot to update debian-ports-archive-keyring.maintscript when
moving the 2016 key to the removed keyring.


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

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

Versions of packages debian-ports-archive-keyring depends on:
ii  apt   1.6~alpha6
ii  gpgv  2.2.4-1

Versions of packages debian-ports-archive-keyring recommends:
ii  gnupg  2.2.4-1

debian-ports-archive-keyring suggests no packages.

-- no debconf information

Bug#886389: dpkg: conffile marked as obsolete after being taken over by different package

[Sven Joachim]

On 2018-01-05 10:44 +0100, Sven Joachim wrote:

> Package: dpkg
> Version: 1.19.0.4
> Severity: normal
>
> After switching from rxvt-unicode-256color to rxvt-unicode (see
> #848284), dpkg-query reports a conffile as obsolete:
>
> ,
> | $ dpkg-query -W -f='${Conffiles}\n' | grep obsolete$
> |  [...]
> |  /etc/X11/app-defaults/URxvt 7b221a2da49507e31f42e702791b085b obsolete
> | $ dpkg -S /etc/X11/app-defaults/URxvt 
> |  rxvt-unicode: /etc/X11/app-defaults/URxvt
> `
>
> This is bogus since the file is shipped in the package, otherwise it
> would belong to rxvt-unicode-256color which was its previous owner.

Purging the rxvt-unicode-256color package helped, although that package
did not contain any files according to "dpkg -L" (I had already removed
but not purged it).  Now the conffile is no longer reported as obsolete.

Cheers,
   Sven

Bug#884771: jetty9 doesn't start anymore

[Chris Donoghue]

Package: jetty9
Version: 9.2.22-3
Followup-For: Bug #884771

Dear Maintainer,

I did a diff between 9.2.22-3 and  9.2.22-2 extracted deb files and
many don't there is missing version strings in the
9.2.22-3 debian package.

Perhaps issue lays there.

File list diff below astached
--- jetty9-2.list   2018-01-05 20:33:19.718186565 +1100
+++ jetty9-3.list   2018-01-05 20:33:25.134286663 +1100
@@ -70,7 +70,7 @@
 ./usr/share/jetty9/lib/annotations/org.objectweb.asm.jar
 ./usr/share/jetty9/lib/apache-jsp
 ./usr/share/jetty9/lib/apache-jsp/jdt-core.jar
-./usr/share/jetty9/lib/apache-jsp/jetty-apache-jsp-9.2.22.v20170531.jar
+./usr/share/jetty9/lib/apache-jsp/jetty-apache-jsp-.jar
 ./usr/share/jetty9/lib/apache-jsp/org.apache.taglibs.taglibs-standard-impl.jar
 ./usr/share/jetty9/lib/apache-jsp/org.apache.taglibs.taglibs-standard-spec.jar
 ./usr/share/jetty9/lib/apache-jsp/tomcat-api.jar
@@ -83,50 +83,50 @@
 ./usr/share/jetty9/lib/apache-jsp/tomcat-util.jar
 ./usr/share/jetty9/lib/ext
 ./usr/share/jetty9/lib/fcgi
-./usr/share/jetty9/lib/fcgi/fcgi-client-9.2.22.v20170531.jar
-./usr/share/jetty9/lib/fcgi/fcgi-server-9.2.22.v20170531.jar
+./usr/share/jetty9/lib/fcgi/fcgi-client-.jar
+./usr/share/jetty9/lib/fcgi/fcgi-server-.jar
 ./usr/share/jetty9/lib/jaspi
 ./usr/share/jetty9/lib/jaspi/javax.security.auth.message.jar
-./usr/share/jetty9/lib/jetty-alpn-client-9.2.22.v20170531.jar
-./usr/share/jetty9/lib/jetty-alpn-server-9.2.22.v20170531.jar
-./usr/share/jetty9/lib/jetty-annotations-9.2.22.v20170531.jar
-./usr/share/jetty9/lib/jetty-cdi-9.2.22.v20170531.jar
-./usr/share/jetty9/lib/jetty-client-9.2.22.v20170531.jar
-./usr/share/jetty9/lib/jetty-continuation-9.2.22.v20170531.jar
-./usr/share/jetty9/lib/jetty-deploy-9.2.22.v20170531.jar
-./usr/share/jetty9/lib/jetty-http-9.2.22.v20170531.jar
-./usr/share/jetty9/lib/jetty-io-9.2.22.v20170531.jar
-./usr/share/jetty9/lib/jetty-jaas-9.2.22.v20170531.jar
-./usr/share/jetty9/lib/jetty-jaspi-9.2.22.v20170531.jar
-./usr/share/jetty9/lib/jetty-jmx-9.2.22.v20170531.jar
-./usr/share/jetty9/lib/jetty-jndi-9.2.22.v20170531.jar
-./usr/share/jetty9/lib/jetty-plus-9.2.22.v20170531.jar
-./usr/share/jetty9/lib/jetty-proxy-9.2.22.v20170531.jar
-./usr/share/jetty9/lib/jetty-quickstart-9.2.22.v20170531.jar
-./usr/share/jetty9/lib/jetty-rewrite-9.2.22.v20170531.jar
-./usr/share/jetty9/lib/jetty-security-9.2.22.v20170531.jar
-./usr/share/jetty9/lib/jetty-server-9.2.22.v20170531.jar
-./usr/share/jetty9/lib/jetty-servlet-9.2.22.v20170531.jar
-./usr/share/jetty9/lib/jetty-servlets-9.2.22.v20170531.jar
-./usr/share/jetty9/lib/jetty-util-9.2.22.v20170531.jar
-./usr/share/jetty9/lib/jetty-webapp-9.2.22.v20170531.jar
-./usr/share/jetty9/lib/jetty-xml-9.2.22.v20170531.jar
+./usr/share/jetty9/lib/jetty-alpn-client-.jar
+./usr/share/jetty9/lib/jetty-alpn-server-.jar
+./usr/share/jetty9/lib/jetty-annotations-.jar
+./usr/share/jetty9/lib/jetty-cdi-.jar
+./usr/share/jetty9/lib/jetty-client-.jar
+./usr/share/jetty9/lib/jetty-continuation-.jar
+./usr/share/jetty9/lib/jetty-deploy-.jar
+./usr/share/jetty9/lib/jetty-http-.jar
+./usr/share/jetty9/lib/jetty-io-.jar
+./usr/share/jetty9/lib/jetty-jaas-.jar
+./usr/share/jetty9/lib/jetty-jaspi-.jar
+./usr/share/jetty9/lib/jetty-jmx-.jar
+./usr/share/jetty9/lib/jetty-jndi-.jar
+./usr/share/jetty9/lib/jetty-plus-.jar
+./usr/share/jetty9/lib/jetty-proxy-.jar
+./usr/share/jetty9/lib/jetty-quickstart-.jar
+./usr/share/jetty9/lib/jetty-rewrite-.jar
+./usr/share/jetty9/lib/jetty-security-.jar
+./usr/share/jetty9/lib/jetty-server-.jar
+./usr/share/jetty9/lib/jetty-servlet-.jar
+./usr/share/jetty9/lib/jetty-servlets-.jar
+./usr/share/jetty9/lib/jetty-util-.jar
+./usr/share/jetty9/lib/jetty-webapp-.jar
+./usr/share/jetty9/lib/jetty-xml-.jar
 ./usr/share/jetty9/lib/jndi
 ./usr/share/jetty9/lib/jndi/javax.mail.jar
 ./usr/share/jetty9/lib/monitor
-./usr/share/jetty9/lib/monitor/jetty-monitor-9.2.22.v20170531.jar
+./usr/share/jetty9/lib/monitor/jetty-monitor-.jar
 ./usr/share/jetty9/lib/servlet-api-3.1.jar
 ./usr/share/jetty9/lib/spring
-./usr/share/jetty9/lib/spring/jetty-spring-9.2.22.v20170531.jar
+./usr/share/jetty9/lib/spring/jetty-spring-.jar
 ./usr/share/jetty9/lib/websocket
-./usr/share/jetty9/lib/websocket/javax-websocket-client-impl-9.2.22.v20170531.jar
-./usr/share/jetty9/lib/websocket/javax-websocket-server-impl-9.2.22.v20170531.jar
+./usr/share/jetty9/lib/websocket/javax-websocket-client-impl-.jar
+./usr/share/jetty9/lib/websocket/javax-websocket-server-impl-.jar
 ./usr/share/jetty9/lib/websocket/javax.websocket-api-1.0.jar
-./usr/share/jetty9/lib/websocket/websocket-api-9.2.22.v20170531.jar
-./usr/share/jetty9/lib/websocket/websocket-client-9.2.22.v20170531.jar
-./usr/share/jetty9/lib/websocket/websocket-common-9.2.22.v20170531.jar
-./usr/share/jetty9/lib/websocket/websocket-server-9.2.22.v20170531.jar
-./usr/share/jetty9/lib/websocket/websocket-servlet-9.2.22.v20170531.jar
+./usr/share/jetty9/lib/websocket/websocket-api-.jar

Bug#886389: dpkg: conffile marked as obsolete after being taken over by different package

[Sven Joachim]

Package: dpkg
Version: 1.19.0.4
Severity: normal

After switching from rxvt-unicode-256color to rxvt-unicode (see
#848284), dpkg-query reports a conffile as obsolete:

,
| $ dpkg-query -W -f='${Conffiles}\n' | grep obsolete$
|  [...]
|  /etc/X11/app-defaults/URxvt 7b221a2da49507e31f42e702791b085b obsolete
| $ dpkg -S /etc/X11/app-defaults/URxvt 
|  rxvt-unicode: /etc/X11/app-defaults/URxvt
`

This is bogus since the file is shipped in the package, otherwise it
would belong to rxvt-unicode-256color which was its previous owner.

Here is the relevant excerpt from the dpkg log:

,
| $ grep rxvt-unicode /var/log/dpkg.log
| 2018-01-05 08:38:30 upgrade rxvt-unicode-256color:i386 9.22-1+b3 9.22-2
| 2018-01-05 08:38:30 status half-configured rxvt-unicode-256color:i386 
9.22-1+b3
| 2018-01-05 08:38:30 status unpacked rxvt-unicode-256color:i386 9.22-1+b3
| 2018-01-05 08:38:30 status half-installed rxvt-unicode-256color:i386 9.22-1+b3
| 2018-01-05 08:38:30 status half-installed rxvt-unicode-256color:i386 9.22-1+b3
| 2018-01-05 08:38:30 status unpacked rxvt-unicode-256color:all 9.22-2
| 2018-01-05 08:38:30 status unpacked rxvt-unicode-256color:all 9.22-2
| 2018-01-05 08:38:30 install rxvt-unicode:i386  9.22-2
| 2018-01-05 08:38:30 status half-installed rxvt-unicode:i386 9.22-2
| 2018-01-05 08:38:30 status unpacked rxvt-unicode:i386 9.22-2
| 2018-01-05 08:38:30 status unpacked rxvt-unicode:i386 9.22-2
| 2018-01-05 08:38:31 configure rxvt-unicode:i386 9.22-2 
| 2018-01-05 08:38:31 status unpacked rxvt-unicode:i386 9.22-2
| 2018-01-05 08:38:31 status unpacked rxvt-unicode:i386 9.22-2
| 2018-01-05 08:38:31 status half-configured rxvt-unicode:i386 9.22-2
| 2018-01-05 08:38:31 status installed rxvt-unicode:i386 9.22-2
| 2018-01-05 08:38:34 configure rxvt-unicode-256color:all 9.22-2 
| 2018-01-05 08:38:34 status unpacked rxvt-unicode-256color:all 9.22-2
| 2018-01-05 08:38:34 status half-configured rxvt-unicode-256color:all 9.22-2
| 2018-01-05 08:38:34 status installed rxvt-unicode-256color:all 9.22-2
| 2018-01-05 08:43:03 status installed rxvt-unicode-256color:all 9.22-2
| 2018-01-05 08:43:03 remove rxvt-unicode-256color:all 9.22-2 
| 2018-01-05 08:43:03 status half-configured rxvt-unicode-256color:all 9.22-2
| 2018-01-05 08:43:03 status half-installed rxvt-unicode-256color:all 9.22-2
| 2018-01-05 08:43:03 status config-files rxvt-unicode-256color:all 9.22-2
| 2018-01-05 08:43:03 status config-files rxvt-unicode-256color:all 9.22-2
`


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

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

Versions of packages dpkg depends on:
ii  libbz2-1.0   1.0.6-8.1
ii  libc62.26-1
ii  liblzma5 5.2.2-1.3
ii  libselinux1  2.7-2
ii  tar  1.29b-2
ii  zlib1g   1:1.2.8.dfsg-5

dpkg recommends no packages.

Versions of packages dpkg suggests:
ii  apt1.6~alpha6
pn  debsig-verify  

-- no debconf information

Bug#884740: RFS: pokemmo/1.4.2-1 [ITP] -- Multiplayer online game based on the Pokemon universe

[Tobias Frost]

Control: tags -1 moreinfo

Hi Carlos,

On Thu, Jan 04, 2018 at 07:05:24PM -0200, Carlos Donizete Froes wrote:
> Hi Tobias,
> 
> > Control: tags -1 moreinfo
> > 
> > Hi Carlos,
> > 
> > you saw the reject from the FTP masters already, I guess.
> > Please update d/copyright and then ping me again.
> > 
> > Tobi
> 
> I have made copyright changes in 'd/copyright'
> 
> Please check mentors.d.n
> 
> https://mentors.debian.net/package/pokemmo

Thanks!

One thing I need to talk to you: Please do NOT modify
already released releases. In other words: NEVER release
different code/stuff using the same version identifier.
This just calls for disaster, as you now have to 1.4.3 in
the wild.

In this case the changes were even not necessary for an
upload. But now I have to ask you to increment the upstream
version number and then ping me again for sponsoring when ready.

For the Debian changes:
Please note that the license grant must be verbose -- a word-by-word
copx of the original text. As the license grant is including
the name of the game, you need to update the grant.
Basically you want the paragraph you have added on top of LICENSE.

--
tobi

 
> Thanks!
> 
> -- 
> ⢀⣴⠾⠻⢶⣦⠀ Carlos Donizete Froes [a.k.a coringao]
> ⣾⠁⢠⠒⠀⣿⡁ - https://wiki.debian.org/coringao
> ⢿⡄⠘⠷⠚⠋⠀ GPG: 4096R/B638B780
> ⠈⠳⣄⠀⠀⠀   2157 630B D441 A775 BEFF  D35F FA63 ADA6 B638 B780

Bug#886375: klystrack: FTBFS (32-bit): error: cast to pointer from integer of different size

[Gürkan Myczko]

Hi Aaron

Thanks for your bug report, I have already forwarded the build issues to 
upstream,

as soon as there's fixes, I'll prepare a new version:

https://github.com/kometbomb/klystrack/issues/222

Best,

Bug#802919: version bump to unison-2.48.4

[Baptiste Jonglez]

On 05-01-18, Benda Xu wrote:
> Benda Xu  writes:
> 
> > Thank you for your comments and diagnosis.  But the bug does not go away
> > by itself.  If you are too busy to bump it, please speak out explicitly.
> > We are willing to help maintaining unison.
> 
> Sorry I have overlooked the upload of unison-2.48.4 on 30 Oct 2017.  The
> version 2.48.4 works well.  Thanks for your efforts, Stéphane.

Oh, good news, thanks Stéphane!

> Shall we close this bug?

It would be nice to push unison 2.48.4 to (at least) stretch-backports
then.

Baptiste


signature.asc
Description: PGP signature

Bug#880407: #880407 xterm: font issue with FreeType 2.8; should not use the rounded ascender and descender

[Vincent Lefevre]

On 2018-01-05 04:13:56 -0500, Thomas Dickey wrote:
> - Original Message -
> | On 2018-01-05 03:59:42 -0500, Thomas Dickey wrote:
> | > Then you should provide more information allowing this to be
> | > reproduced.
> | 
> | I can reproduce this with the default config and:
> | 
> |   xterm -fa Monospace -fs 10 -xrm "Xft.dpi: 132"
> | 
> | (the "Xft.dpi: 132" is important).
> 
> I did that (and other values of ".dpi") without seeing any other effect than
> the one for which I made a workaround: detecting the improper rounding and
> forcing xterm's internal line-drawing in that case.  The line-drawing glyphs
> were effectively shorter than some of the other characters.

Sorry, I don't understand what you mean. Can you reproduce the problem
with that?

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#886388: rxvt: obsolete conffile left on the system

[Sven Joachim]

Package: rxvt
Version: 1:2.7.10-7.1+urxvt9.22-2
Severity: normal

Upgrading from 1:2.7.10-7+b1 left the obsolete conffile
/etc/menu-methods/rxvt on my system.  The preinst script makes this file
non-executable, but it really should also be removed.  Please refer to
dpkg-maintscript-helper(1) and dh_installdeb(1) how to that.

Thanks for taking care of the rxvt → rxvt-unicode transition! :-)


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

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

Versions of packages rxvt depends on:
ii  rxvt-unicode  9.22-2

rxvt recommends no packages.

rxvt suggests no packages.

-- no debconf information

Bug#849691: RFS: gnome-shell-extension-radio/8-1 [ITP] -- GNOME shell

[Tobias Frost]

On Thu, Jan 04, 2018 at 06:23:33PM +, l...@ndrs.fr wrote:
> Hi Tobias,
> 
> I fixed the version and the changelog, I was not sure about it when I bumped 
> it.
> 
> I also fixed d/copyright.
> 
> Thanks for the review.
> 
> I uploaded a new version to mentors.d.n. but it's not showing for the moment, 
> will wait and see.
> Maybe I did something wrong when I deleted the package and uploaded it again.

Yes, something must have gone wrong. It is hard to tell remotely though, so I 
can only guess:
- maybe signing failed?
- incomplete upload?

BTW, you do not need to delete an upload beforehand, IIRC just uploading does 
it too.

(Note when you reupload, please reopen the RFS-bug -- a bot closed it tonight 
-- but do
not open up a new one..)

Looking forward for your updated package!

-- 
Tobi

> 
> -- Léo

Bug#886387: linux-image-4.14.0-0.bpo.2-amd64: When booting with the latest 4.14+88~bpo9+1 kernel GDM fails to start

[Sean Clarke]

Package: src:linux
Version: 4.14.7-1~bpo9+1
Severity: important

Dear Maintainer,

System updated from backports, rebooted, GDM fails, rolledback kernel version
to previous (running now) and all is OK.



-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
sys_vendor: Alienware
product_name: Alienware Area-51 R2
product_version: 
chassis_vendor: Alienware
chassis_version: 
bios_vendor: Alienware
bios_version: A10
board_vendor: Alienware
board_name: 09G12C
board_version: A00

** Network interface configuration:

source /etc/network/interfaces.d/*

auto lo
iface lo inet loopback

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 
v4/Xeon D DMI2 [8086:6f00] (rev 01)
Subsystem: Dell Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DMI2 [1028:064c]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 

00:01.0 PCI bridge [0604]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 
v4/Xeon D PCI Express Root Port 1 [8086:6f02] (rev 01) (prog-if 00 [Normal 
decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport
Kernel modules: shpchp

00:01.1 PCI bridge [0604]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 
v4/Xeon D PCI Express Root Port 1 [8086:6f03] (rev 01) (prog-if 00 [Normal 
decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport
Kernel modules: shpchp

00:02.0 PCI bridge [0604]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 
v4/Xeon D PCI Express Root Port 2 [8086:6f04] (rev 01) (prog-if 00 [Normal 
decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport
Kernel modules: shpchp

00:03.0 PCI bridge [0604]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 
v4/Xeon D PCI Express Root Port 3 [8086:6f08] (rev 01) (prog-if 00 [Normal 
decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport
Kernel modules: shpchp

00:05.0 System peripheral [0880]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon 
E3 v4/Xeon D Map/VTd_Misc/System Management [8086:6f28] (rev 01)
Subsystem: Dell Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D 
Map/VTd_Misc/System Management [1028:064c]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 

00:05.1 System peripheral [0880]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon 
E3 v4/Xeon D IIO Hot Plug [8086:6f29] (rev 01)
Subsystem: Dell Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D IIO Hot Plug 
[1028:064c]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 

00:05.2 System peripheral [0880]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon 
E3 v4/Xeon D IIO RAS/Control Status/Global Errors [8086:6f2a] (rev 01)
Subsystem: Dell Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D IIO RAS/Control 
Status/Global Errors [1028:064c]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 

00:05.4 PIC [0800]: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D 
I/O APIC [8086:6f2c] (rev 01) (prog-if 20 [IO(X)-APIC])
Subsystem: Dell Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D I/O APIC 
[1028:064c]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 

00:11.0 Unassigned class [ff00]: Intel Corporation C610/X99 series chipset SPSR 
[8086:8d7c] (rev 05)

Bug#886377: (Why don't try to port GNU/Hurd, GNU/KFreeBSD on QL Sinclair with 68040/68060?)

[pdb]

Why don't try to port of: GNU/HURD, GNU/KFreeBSD on QL Sinclair with 68040
or 68060? (Paolo Del Bene)

Have you ever thinked to port GNU/HURD and/or GNU/KFreeBSD on QL Sinclair
with cpu 68040/68060?

Awaiting for your reply as soon as possible,

Greetings,

Paolo Del Bene iw0fzw

Bug#880407: #880407 xterm: font issue with FreeType 2.8; should not use the rounded ascender and descender

[Thomas Dickey]

- Original Message -
| From: "Vincent Lefevre" 
| To: "Thomas Dickey" 
| Cc: 880...@bugs.debian.org
| Sent: Friday, January 5, 2018 4:09:08 AM
| Subject: Re: Bug#880407: #880407 xterm: font issue with FreeType 2.8; should 
not use the rounded ascender and
| descender
| 
| On 2018-01-05 03:59:42 -0500, Thomas Dickey wrote:
| > Then you should provide more information allowing this to be
| > reproduced.
| 
| I can reproduce this with the default config and:
| 
|   xterm -fa Monospace -fs 10 -xrm "Xft.dpi: 132"
| 
| (the "Xft.dpi: 132" is important).

I did that (and other values of ".dpi") without seeing any other effect than
the one for which I made a workaround: detecting the improper rounding and
forcing xterm's internal line-drawing in that case.  The line-drawing glyphs
were effectively shorter than some of the other characters.

-- 
Thomas E. Dickey 
http://invisible-island.net
ftp://ftp.invisible-island.net

Bug#880407: #880407 xterm: font issue with FreeType 2.8; should not use the rounded ascender and descender

[Vincent Lefevre]

On 2018-01-05 03:59:42 -0500, Thomas Dickey wrote:
> Then you should provide more information allowing this to be reproduced.

I can reproduce this with the default config and:

  xterm -fa Monospace -fs 10 -xrm "Xft.dpi: 132"

(the "Xft.dpi: 132" is important).

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#880407: #880407 xterm: font issue with FreeType 2.8; should not use the rounded ascender and descender

[Thomas Dickey]

- Original Message -
| From: "Vincent Lefevre" 
| To: dic...@his.com, 880...@bugs.debian.org
| Sent: Friday, January 5, 2018 2:30:51 AM
| Subject: Bug#880407: #880407 xterm: font issue with FreeType 2.8; should not 
use the rounded ascender and descender
| 
| Control: reopen -1
| Control: found -1 331-1
| Control: tags -1 - fixed-upstream
| 
| On 2017-12-30 14:53:27 -0500, Thomas Dickey wrote:
| > I investigated, found that it is a defect in FreeType.
| > None of the comments in
| > 
| > https://savannah.nongnu.org/bugs/?52165
| > 
| > were helpful (some of the information is incorrect).
| > 
| > I made a workaround for this problem in patch #331.
| 
| It still has the same problems: xterm higher than before for the
| same number of text lines, and a black line between text lines.

Then you should provide more information allowing this to be reproduced.

-- 
Thomas E. Dickey 
http://invisible-island.net
ftp://ftp.invisible-island.net