Bug#880554: [Pkg-xen-devel] Bug#880554: Bug#880554: xen domu freezes with kernel linux-image-4.9.0-4-amd64

[Valentin Vidic]

On Tue, Feb 27, 2018 at 08:22:50PM +0100, Valentin Vidic wrote:
> Since I can't reproduce it easily anymore I suspect something was
> fixed in the meanwhile.  My original report was for 4.9.30-2+deb9u2
> and since then there seems to be a number of fixes that could be
> related to this:

Just rebooted both dom0 and domU with 4.9.30-2+deb9u2 and the the
postgresql domU is having problems right away after boot:

  domid=1: nr_frames=32, max_nr_frames=32

  [  242.652100] INFO: task kworker/u90:0:6 blocked for more than 120 seconds.

Upgrading the kernels and I can't get it above 11 anymore:

  domid=1: nr_frames=11, max_nr_frames=32

So some of those many kernel fixes did the trick and things just
work fine with the newer kernels without raising gnttab_max_frames.

-- 
Valentin

Bug#891710: ITP: node-compare-versions -- Version string comparison for Node.js

[Julien Puydt]

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

* Package name: node-compare-versions
  Version : 3.1.0
  Upstream Author : Ole Bjørn Michelsen 
* URL : https://github.com/omichelsen/compare-versions#readme
* License : Expat
  Programming Lang: JavaScript
  Description : Version string comparison for Node.js
 This package provides a comparison function for version strings
 following the semver specification.


I'm interested in packaging it because it's a dep of something I need to
update one of my existing packages.

It's quite widely used :
$ npm2deb rdepends compare-versions|wc -l
89

Snark on #debian-js

Bug#891711: ITP: node-coffee-loader -- coffee loader module for webpack

[Pirate Praveen]

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

* Package name: node-coffee-loader
  Version : 0.9.0
  Upstream Author : Tobias Koppers @sokra
* URL : http://github.com/webpack-contrib/coffee-loader
* License : Expat
  Programming Lang: JavaScript
  Description : coffee loader module for webpack

 This package enables using coffeescript files directly from webpack.
 .
 Webpack packs/bundles CommonJs/AMD modules for the browser.
 .
 Node.js is an event-based server-side JavaScript engine.

In dependency chain of gitlab 9.5 (build dependency of deckar01-task_list)



signature.asc
Description: OpenPGP digital signature

Bug#891709: rtaudio library writes debug info to stderr

[John Belmonte]

Package: rtaudio
Severity: important

Dear Maintainer,

Please remove --enable-debug compilation from the rtaudio build.
It causes debug info to be written to stderr, such as ALSA
device details:

  RtApiAlsa: dump hardware params just after device open:

  ACCESS:  MMAP_INTERLEAVED RW_INTERLEAVED
  FORMAT:  S16_LE S24_LE
  SUBFORMAT:  STD
  SAMPLE_BITS: [16 32]
  FRAME_BITS: [16 96]
  ...

Clients using the rtaudio library should have control over
what's emitted on stdio.  If the info is important for some use
cases, please ask upstream to put the logging under runtime
control.

Regards,
--John

Bug#758317: Daugiabučių, gyvenamųjų namų, sodų bendrijų bazė su pirmininkų kontaktais

[Egidijus Stanaitis]

Sveiki,

 

Ar Jums reikia bendrijų bazės?

 

Daugiabučių, gyvenamųjų namų, sodų bendrijų bazė su pirmininkų kontaktais

 

Bazėje nurodomi šie duomenys

 

Bendrijos pavadinimas

Bendrijos kodas

SD kodas

Įregistravimo data

Darbuotojų skaičius

Elektroninio pašto adresas

Mobilus telefonas 

Bendrijos adresas 

Miestas

Pašto kodas

Bendrijos pirmininko vardas pavardė

 

Visos bendrijos veikiančios su pirmininkų kontaktais

 

Bendrijų bazę galima filtruoti pagal miestus, registracijos datą

 

Ši bazė gali būti naudinga ieškant klientų

 

Ar Jums atsiųsti bendrijų bazės pavyzdį su pasiūlymu?

 

Turime ir asociacijų, valstybinių institucijų, įmonių, ūkininkų bazių.

Kokių Jums dar reikia bazių?

 

Taip pat siunčiame naujienlaiškius

Išrašome sąskaitą faktūrą

 

 

Pagarbiai,

Egidijus Stanaitis

+370 603 160 22

teradi...@gmail.com

Bug#891295: blueman: fails to switch bluetooth back if it was disabled before shutdown

[Christopher Schramm]

Hi Alexander,

> If one selects the blueman applet from the LXDE menu, it fails to start saying
> "Bluez daemon is not running, blueman-manager cannot continue. This probably
> means that there were no Bluetooth adapters detected or Bluetooth daemon was
> not started".

That message is triggered if the DBus name org.bluez is not available.
What does

  systemctl status bluetooth.service

show you?

Bug#849015: Daugiabučių, gyvenamųjų namų, sodų bendrijų bazė su pirmininkų kontaktais

[Egidijus Stanaitis]

Sveiki,

 

Ar Jums reikia bendrijų bazės?

 

Daugiabučių, gyvenamųjų namų, sodų bendrijų bazė su pirmininkų kontaktais

 

Bazėje nurodomi šie duomenys

 

Bendrijos pavadinimas

Bendrijos kodas

SD kodas

Įregistravimo data

Darbuotojų skaičius

Elektroninio pašto adresas

Mobilus telefonas 

Bendrijos adresas 

Miestas

Pašto kodas

Bendrijos pirmininko vardas pavardė

 

Visos bendrijos veikiančios su pirmininkų kontaktais

 

Bendrijų bazę galima filtruoti pagal miestus, registracijos datą

 

Ši bazė gali būti naudinga ieškant klientų

 

Ar Jums atsiųsti bendrijų bazės pavyzdį su pasiūlymu?

 

Turime ir asociacijų, valstybinių institucijų, įmonių, ūkininkų bazių.

Kokių Jums dar reikia bazių?

 

Taip pat siunčiame naujienlaiškius

Išrašome sąskaitą faktūrą

 

 

Pagarbiai,

Egidijus Stanaitis

+370 603 160 22

teradi...@gmail.com

Bug#837081: netbeans: Crashes due to assertion failure in GLib

[Mark Cave-Ayland]

On 25/02/18 00:16, Samuel Thibault wrote:


I have investigated, and yes there are leaks there.  It'll be quite
invasive to fix, so I won't be able to push that to stretch.  But I
believe if you can confirm that at least the crashes are gone, we can
push the fix to stretch.


Hi Samuel,

Just to confirm that after 2 days I've seen no console warnings/errors 
or experienced any crashes here with your proposed stretch packages, so 
I believe they are working well.


I've now just upgraded to your latest -20 packages to give them a more 
thorough testing, and will keep an eye on the memory usage over the 
course of the day.



Many thanks,

Mark.

Bug#891695: "mh_linkjar" and "mh_installpoms" Do Not Support "--relocate"

[Emmanuel Bourg]

Le 28/02/2018 à 03:46, 殷啟聰 | Kai-Chung Yan a écrit :

> If I use "jh_maven_repo_helper" and then add a "relocate" option to 
> ".poms", "mh_linkjar" shows the following error:
> 
>> Invalid option: relocate

What syntax did you use in debian/.poms?


> So I move the "relocate" option to "debian/rules" as
> 
> ```make
> override_mh_installpoms:
>     mh_installpoms --relocate=org.osgi:org.osgi.compendium:debian
> ``
> 
> This time, "mh_installpoms" shows said error.

--relocate doesn't make sense with mh_installpoms, because
mh_installpoms install several poms but --relocate is only for one pom.

Emanuel Bourg

Bug#891708: ITP: python-appsettings -- Argparse wrapper that supports fallback settings in env vars and/or a yaml file

[Simon Spöhel]

Package: wnpp

* Package name  : python-appsettings
  Upstream url  : https://pypi.org/project/appsettings/
* License   : MIT
  Description	: Argparse wrapper that supports fallback settings in env 
vars and/or a yaml file




Greetings
Simon

Bug#891707: ITP: pyqtqwt -- Python version of the Qwt6 technical widget library (Python3)

[Gudjon I. Gudjonsson]

Package: wnpp Owner: "Gudjon I. Gudjonsson"  

 extends the Qt framework with widgets for scientific and engineering 
 applications. It provides a widget to plot 2-dimensional data and various 
 widgets to display and control bounded or unbounded floating point values.
 .
 This version is compiled against Qt5.



The package will replace PyQwt5 which builds on obsolete versions of Qt and Qwt.
Qwt5 and Qt4 which will both be removed from Debian soon. PyQt-Qwt builds on
Python3 (and 2) and Qt5 (and 4), Qwt6 which are all current versions of the 
libraries.


[1] http://qwt.sourceforge.net/qwtlicense.html

Bug#880554: [Pkg-xen-devel] Bug#880554: Bug#880554: xen domu freezes with kernel linux-image-4.9.0-4-amd64

[Christian Schwamborn]

I much appreciate the effort you all did and like the idea to ship the 
xen-diag tool and maybe a hint somewhere about the issues that occurred 
and the possible solution by raising max_nr_frames.


On 27.02.2018 17:05, Hans van Kranenburg wrote:

ad 1. Christian, Valentin, can you give more specific info that can help
someone else to set up a test environment to trigger > 32 values.


As this isn't my own system, but a productive system of one of my 
customers, I'm really reluctant to use it for invasive testing.


Just for recap: The issues hit me with kernel 4.9.51-1

hardware:
xeon E5-2620 v4
board supermicro X10SRi-F
32gb ecc ram
two 10tb server disk
two I350 network adapter (onboard)

dom0:
debian stretch (up to date), kernel 4.9.51-1, xen-hypervisor 4.8.1-1+deb9u3,
the two network as adapter as a bond in a bridge
the discs: gpt, 4 part (1M, 256M esp, 256M md mirror for boot, rest as 
md mirror for lvm)


domu:
memory: 8192, 2 vcpus
uses a network interface on the bridge
16 lvm volumes as phys devices
debian stretch
issue with both kernel versions: 4.9.30-2+deb9u5 and 4.9.51-1
system runs mostly some smb, some web services, cal/card dav, psql, 
ldap, postfix, cyrus ...


In my early tests before the issue was discussed here I tried 
linux-image-4.13.0-0.bpo.1-amd64 an the system went stable for a week.


Oh and It's worth to mention that I tried thin lvm in the beginning, but 
I dropped that due to (write)performance and boot issues (thinpool was 
always inactive after boot and took about 5-10 minutes to activate after 
there where about 4TB of data within).


currently the system is running stable with max_nr_frames=256 (I wanted 
to be on the save side) and kernel 4.9.65-3+deb9u2.


Maybe I can try to get some values with xen-diag Valentin provided to 
see the current state of the system, but I'm really busy at the moment 
job wise and private, I hope next week gets better (had some bad luck 
with our water installation - much mopping).

Bug#785665: [pkg-ntp-maintainers] Bug#785665: ntp: support for atom driver not included

[Richard Laager]

On 01/10/2018 11:03 PM, Daniel M. Weeks wrote:
> On Wed, 8 Nov 2017 05:00:50 -0600 Richard Laager wrote:
>> I recommend *against* enabling ATOM support.

I retract the above statement. Sorry for the noise.

I must have been thinking of a different driver. Driver 22 (REFID "PPS")
in ntpd/refclock_atom.c is useful in certain scenarios. I used it myself
with a Symmetricom clock using the WWVB driver, and continue to use
those drivers with NTPsec. So now that I'm thinking of the right driver,
I now agree that it is desirable to have built.

Driver 22 was working out-of-the-box for me, but that was on an Ubuntu
(Xenial) system and not Debian. Ubuntu had enabled PPS support with a
Build-Depends on pps-tools (plus some documentation updates). I see that
the ntp package in Debian currently has a Build-Depends on pps-tools (on
linux-any). Ubuntu didn't need --enable-ATOM for it to get built.

>> It is much better to use SHM to talk to gpsd. Here are a whole bunch of
>> details:
>> http://www.catb.org/gpsd/gpsd-time-service-howto.html
>>
> There is nothing in that document that discourages ATOM.

The link was to show the alternative approach (SHM talking to gpsd). I
still recommend this approach instead of driver 22 for Raspberry Pi GPS
Stratum 1 systems.

-- 
Richard

Bug#880554: [Pkg-xen-devel] Bug#880554: Bug#880554: xen domu freezes with kernel linux-image-4.9.0-4-amd64

[Christian Schwamborn]

I much appreciate the effort you all did and like the idea to ship the 
xen-diag tool and maybe a hint somewhere about the issues that occurred 
and the possible solution by raising max_nr_frames.


On 27.02.2018 17:05, Hans van Kranenburg wrote:

ad 1. Christian, Valentin, can you give more specific info that can help
someone else to set up a test environment to trigger > 32 values.


As this isn't my own system, but a productive system of one of my 
customers, I'm really reluctant to use it for invasive testing.


Just for recap: The issues hit me with kernel 4.9.51-1

hardware:
xeon E5-2620 v4
board supermicro X10SRi-F
32gb ecc ram
two 10tb server disk
two I350 network adapter (onboard)

dom0:
debian stretch (up to date), kernel 4.9.51-1, xen-hypervisor 4.8.1-1+deb9u3,
the two network as adapter as a bond in a bridge
the discs: gpt, 4 part (1M, 256M esp, 256M md mirror for boot, rest as 
md mirror for lvm)


domu:
memory: 8192, 2 vcpus
uses a network interface on the bridge
16 lvm volumes as phys devices
debian stretch
issue with both kernel versions: 4.9.30-2+deb9u5 and 4.9.51-1
system runs mostly some smb, some web services, cal/card dav, psql, 
ldap, postfix, cyrus ...


In my early tests before the issue was discussed here I tried 
linux-image-4.13.0-0.bpo.1-amd64 an the system went stable for a week.


Oh and It's worth to mention that I tried thin lvm in the beginning, but 
I dropped that due to (write)performance and boot issues (thinpool was 
always inactive after boot and took about 5-10 minutes to activate after 
there where about 4TB of data within).


currently the system is running stable with max_nr_frames=256 (I wanted 
to be on the save side) and kernel 4.9.65-3+deb9u2.


Maybe I can try to get some values with xen-diag Valentin provided to 
see the current state of the system, but I'm really busy at the moment 
job wise and private, I hope next week gets better (had some bad luck 
with our water installation - much mopping).

Bug#891630: Missing dep making it unusable

[Pirate Praveen]

On Tue, 27 Feb 2018 07:18:00 -0700 TheSin  wrote:
> After upgrading, and trying to bundle gitlab I get
> 
> Could not find gem 'deckar01-task_list (>= 1.0.5, ~> 1.0)' in any of the gem 
> sources listed in your Gemfile.
> 
> From 
> /usr/share/rubygems-integration/all/specifications/deckar01-task_list-2.0.0.gemspec
>  in ruby-task-list but there is no depends to satisfy this.
> 
> Fix for now is I reinstalled 1.0.1 to get things working again.
> 

This was uploaded in preparation of gitlab 9.5 upload to unstable.
Though https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890877#10 is
blocking the upload.



signature.asc
Description: OpenPGP digital signature

Bug#888391: lynx: RUBOUT deletes character in FRONT of the cursor instead of BEHIND

[Axel Beckert]

Hi Thomas,

thanks for digging into this. It seems to me that this is partially
caused by different expectations and partially by not being aware,
which Lynx settings change the mentioned behaviour.

Thomas Dickey wrote:
> On Thu, Jan 25, 2018 at 03:04:51PM +0100, Axel Beckert wrote:
> > > > I've tested all lynx versions available in supported Debian releases
> > > > and found that those lynx versions in
> > > >
> > > > * Debian Unstable/Buster (2.8.9dev16-2),
> > > > * Debian 9 Stretch (2.8.9dev11-1), and
> > > > * Debian 8 Jessie (2.8.9dev1-2)
> > > >
> > > > exhibit this behaviour, but not the lynx version in
> > > >
> > > > * Debian 7 Wheezy (2.8.8dev.12-2).

Given your hints what might be relevant, namely the "Line edit style"
setting, I must admit that this setting has been different on the
Debian 7 box I used for testing. There I had "Bash-like Bindings".
Otherwise I had "Default Bindings". Which according to the table below
explains very well, why I had a different result there. And changing
it to "Bash-like Bindings" changes my Debian 7 box to exhibit the same
behaviour as the others.

> > > And as mentioned in (an older, hasn't been updated for years) OpenBSD .
> 
> hmm - I have VMs for Debian 5-9 (and some others), but checking
> Debian 6-9, I don't see the behavior described.
[...]
> Here's some data noted while editing text-fields in the options menu:
>
> DebianLynxKeyboardBackspace   Delete  
> Del
> 
> 6 2.8.8dev.5-1bashDELPDELNnone
> 6 2.8.8dev.5-1alternate   DELPDELPnone
> 6 2.8.8dev.5-1default DELPDELPnone
> 
> 7 2.8.8dev.12-2+deb7u2 bash   DELPDELNnone
> 7 2.8.8dev.12-2+deb7u2 alternate  DELPDELPnone
> 7 2.8.8dev.12-2+deb7u2 defaultDELPDELPnone
> 
> 8 2.8.9dev1-2+deb8u1 bash DELPDELNnone
> 8 2.8.9dev1-2+deb8u1 alternateDELPDELPnone
> 8 2.8.9dev1-2+deb8u1 default  DELPDELPnone
> 
> 9 2.8.9dev11-1bashDELPDELNnone
> 9 2.8.9dev11-1alternate   DELPDELPnone
> 9 2.8.9dev11-1default DELPDELPnone
>
> referring to the section in lynx.cfg discussing keymap:
> #  DELN   # Delete next/curr char
> #  DELP   # Delete prev  char

Which means for me that all Lynx versions in Debian 6 to 9 with "Line
edit-style" (I assume that's meant with "keyboard") set to anything
else than "Bash-like Bindings" exhibit the reported, but unexpected
behaviour of "Delete" deleting the previous character (DELP) instead
of the next/current one (DELN).

As I understood the original reporter, he expects that Delete always
does DELN and never does DELP. And I actually expect this behaviour,
too, hence the "confirmed" tag.
 
> in xterm (the names correspond to a DEC VT220).  In Linux console, that
> "Del" sends the same escape sequence as "Delete".
[...]
> If I've overlooked some detail, steps-to-reproduce would be helpful.

JFTR: How I tested:

* My Lynx has "Line edit style" set to "Default Bindings" (except on
  the one box as mentioned above).
* Took an uxterm.
* I called "lynx https://duckduckgo.com/lite;, navigated to the search
  box, typed a few characters, then pressed the cursor left key a few
  times and pressed "Delete" to see which character will be deleted.
* Second test was doing the same, but in the Editor text field of the
  options. No difference here.
* In case of remote boxes (all but Debian Unstable) I used "ssh -t
  lynx ..." inside the uxterm on Debian Unstable.

Hope this helps to clarify where an issue is seen and under which
circumstances it shows up.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#873094: RFS: granite/0.4.1-1 [ITP]

[Tobias Frost]

Am 28. Februar 2018 05:53:31 MEZ schrieb Yangfl :
>2018-02-28 2:30 GMT+08:00 Tobias Frost :
>> Homework:
>> - please manually remove the package from mentors. (as it has to pass
>NEW)
>
>IIRC the package will be auto-removed, isn't it?

After being accepted, yes. But until then it will show up on the list of 
packages needing sponsoring. To avoid that someone looks at it and waste time 
on it, simply manually delete it.

>> Future uploads:
>> - please add a dep3 header to the patch.
>> - there are tons of depereciation warnings in the upstream code..
>please ask upstream or work towards fixing them...
>
>I can't see anything like 'deprecate' from cmake log. Did I miss
>something?

Not cmake.
Iirc gtk depreciation messages in the build log.

Bug#888510: stretch-pu: package xmltooling/1.6.0-4

[Adam D. Barratt]

Hi,

On Wed, 2018-02-28 at 06:45 +0100, Salvatore Bonaccorso wrote:
> Hi
> 
> On Fri, Feb 23, 2018 at 04:51:23PM +, Adam D. Barratt wrote:
> > Control: tags -1 + moreinfo
> > 
> > On Fri, 2018-01-26 at 15:31 +0100, Ferenc Wágner wrote:
> > > The Security Team advised that CVE-2018-0486 should be fixed by a
> > > stable
> > > update, because it isn't exploitable in the stretch version of
> > > the
> > > Shibboleth stack, but software outside Debian could still be
> > > affected
> > > by the issue.  Stretch currently has version 1.6.0; upstream
> > > fixed
> > > this
> > > security issue in 1.6.3 (already uploaded to unstable).  Since
> > > 1.6.2
> > > was
> > > a revert of the most part of the changes in 1.6.1, 1.6.3 is
> > > effectively
> > > three code changes beyond 1.6.0: the security fix itself:
> > 
> > [...]
> > > Based on the above, a stable update straight to 1.6.3 does not
> > > seem
> > > unreasonable to me, but it's your call, certainly.  Backporting
> > > the
> > > first hunk (the relevant security fix) is easy enough.  On the
> > > other
> > > hand, having version numbers reflecting the reality can be
> > > useful.
> > 
> > Indeed, that doesn't seem entirely unreasonable.
> > 
> > > So, what version number should I post the debdiff for?  Please
> > > include the Debian part as well, I haven't prepared stable
> > > updates
> > > yet.
> > 
> > 1.6.3-1~deb9u1, in this case.
> > 
> > > Also, if you can estimate: when can we expect the next stable
> > > update,
> > > that is, how much time have I got for this process?
> > 
> > We can do better than that - the window for the next point release
> > closes next weekend. Of course, if you don't make that, there'll
> > always
> > be the next time.
> 
> FTR, there was a xmltooling DSA yesterday including the fix. But I
> guess the basic question remains if xmltooling still can be updated
> to
> 1.6.3 (or now 1.6.4 based version?) for stretch.

I was under the impression from the above exchange that Ferenc was
going to provide a debdiff so we could see exactly what that looked
like. I guess that now wants to be relative to the security update.

Regards,

Adam

Bug#888510: stretch-pu: package xmltooling/1.6.0-4

[Salvatore Bonaccorso]

Hi

On Fri, Feb 23, 2018 at 04:51:23PM +, Adam D. Barratt wrote:
> Control: tags -1 + moreinfo
> 
> On Fri, 2018-01-26 at 15:31 +0100, Ferenc Wágner wrote:
> > The Security Team advised that CVE-2018-0486 should be fixed by a
> > stable
> > update, because it isn't exploitable in the stretch version of the
> > Shibboleth stack, but software outside Debian could still be affected
> > by the issue.  Stretch currently has version 1.6.0; upstream fixed
> > this
> > security issue in 1.6.3 (already uploaded to unstable).  Since 1.6.2
> > was
> > a revert of the most part of the changes in 1.6.1, 1.6.3 is
> > effectively
> > three code changes beyond 1.6.0: the security fix itself:
> [...]
> > Based on the above, a stable update straight to 1.6.3 does not seem
> > unreasonable to me, but it's your call, certainly.  Backporting the
> > first hunk (the relevant security fix) is easy enough.  On the other
> > hand, having version numbers reflecting the reality can be useful.
> 
> Indeed, that doesn't seem entirely unreasonable.
> 
> > So, what version number should I post the debdiff for?  Please
> > include the Debian part as well, I haven't prepared stable updates
> > yet.
> 
> 1.6.3-1~deb9u1, in this case.
> 
> > Also, if you can estimate: when can we expect the next stable update,
> > that is, how much time have I got for this process?
> 
> We can do better than that - the window for the next point release
> closes next weekend. Of course, if you don't make that, there'll always
> be the next time.

FTR, there was a xmltooling DSA yesterday including the fix. But I
guess the basic question remains if xmltooling still can be updated to
1.6.3 (or now 1.6.4 based version?) for stretch.

Regards,
Salvatore

Bug#891706: ITP: golang-github-tonistiigi-fsutil -- Incremental file directory sync tools in golang

[Arnaud Rebillout]

Package: wnpp
Severity: wishlist
Owner: Arnaud Rebillout 

* Package name: golang-github-tonistiigi-fsutil
  Version : 0.0~git20180109.0b8b62d-1
  Upstream Author : Tõnis Tiigi
* URL : https://github.com/tonistiigi/fsutil
* License : Expat
  Programming Lang: Go
  Description : Incremental file directory sync tools in golang.



- why is this package useful/relevant?

It is a dependency of docker.

- how do you plan to maintain it?

I plan to maintain it within the golang packaging team.

Bug#459427: changelog vs. NEWS handling

[Sean Whitton]

Hello,

On Tue, Feb 27 2018, Adrian Bunk wrote:

> Policy should define the naming before dh_installchangelogs should
> change.

Please expand on why you think this is the way we have to proceed.

We try to have Policy reflect changes already in the archive, rather
than the other way around, except in situations where that can't make
sense.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#873094: RFS: granite/0.4.1-1 [ITP]

[Yangfl]

2018-02-28 2:30 GMT+08:00 Tobias Frost :
> Homework:
> - please manually remove the package from mentors. (as it has to pass NEW)

IIRC the package will be auto-removed, isn't it?

> Future uploads:
> - please add a dep3 header to the patch.
> - there are tons of depereciation warnings in the upstream code.. please ask 
> upstream or work towards fixing them...

I can't see anything like 'deprecate' from cmake log. Did I miss something?

Bug#891705: Apparmor policy prevents chown/chmod of the Unix control socket

[Simon Deziel]

Package: unbound
Version: 1.6.7-1

Dear maintainer,

An Ubuntu user reported an issue [1] with the unbound's Apparmor profile
that prevents unbound from chown'ing and chmod'ing the Unix control
socket if used (non-default). To reproduce:

# cat << EOF > /etc/unbound/unbound.conf.d/remote-control.conf
remote-control:
 control-enable: yes
 control-interface: /run/unbound.ctl
EOF
# service unbound restart
# ls -l /run/unbound.ctl

Without the fix, ls -l returns this:

srw-rw 1 root root 0 Feb 23 18:40 /run/unbound.ctl=

But should return:

srw-rw 1 unbound unbound 0 Feb 23 18:38 /run/unbound.ctl=

Regards,
Simon


1: https://bugs.launchpad.net/ubuntu/+source/unbound/+bug/1749931

Bug#891704: fping broken with kernel ipv6.disable=1

[Dean Hamstead]

Package: fping
Version: 4.0-6
Severity: important

Dear Maintainer,

fping is broken with the kernel is given the option ipv6.disable=1

See https://github.com/schweikert/fping/issues/118 (patch being worked
on)
Also https://github.com/voidlinux/void-packages/issues/6456

My symptoms are exactly as above, so i wont post them redundantly


-- Package-specific info:
-rwxr-xr-x 1 root root 43904 Jan  2 20:13 /usr/bin/fping
lrwxrwxrwx 1 root root 5 Jan  2 20:13 /usr/bin/fping6 -> fping
/usr/bin/fping = cap_net_raw+ep

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

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

Versions of packages fping depends on:
ii  libc62.26-6
ii  libcap2-bin  1:2.25-1.2
ii  netbase  5.4

fping recommends no packages.

fping suggests no packages.

-- no debconf information


Psst! It's possible that this email contains information that is on the super 
secret side of confidential. So if you received it accidentally, let the sender 
know straight away and delete it (and the email you sent them). Also, we should 
let you know that any emails that come and go through Winc might be 
scanned, stored or read by Winc at its discretion. If you've got a 
question, please give us a buzz on +61 2 9335 0555 (Australia) or +64 9 271 
7600 (NZ). Oh, and Winc does its best to avoid errors on emails it 
sends, but we can't promise that it will be error free. So, please don't hold 
it against us.

Bug#891703: mailman3-suite: DB user isn't read from setting_local (mailman3-suite.py in /etc)

[Eric Côté]

Package: mailman3-suite
Version: 0+20170523-10
Severity: important

Hi,

The default user is being read from the packaged settings.py instead of the 
settings_local.py file symlinked to /etc/mailman3 .
I see error logs saying "mailmansuite" has no access, which is true since 
that's not what I configured. I had to hand edit
the /usr/share/mailman3-suite/settings.py by hand to have to work like I wanted 
(which isn't recommended, nor what I would like to do).

Is there some solution to this?

Thank you
Eric

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

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

Versions of packages mailman3-suite depends on:
ii  dbconfig-mysql2.0.9
ii  dbconfig-pgsql2.0.9
ii  dbconfig-sqlite3  2.0.9
ii  debconf [debconf-2.0] 1.5.65
ii  lsb-base  9.20170808
ii  node-less 1.6.3~dfsg-2
ii  python2.7.14-4
ii  python-django-hyperkitty  1.1.4-3
ii  python-django-postorius   1.1.2-1
ii  python-psycopg2   2.7.4-1
ii  python-whoosh 2.7.4+git6-g9134ad92-1
ii  python3-pymysql   0.8.0-1
ii  ruby-sass 3.5.3-1
ii  ucf   3.0038
ii  uwsgi 2.0.15-10.2
ii  uwsgi-plugin-python   2.0.15-10.2

Versions of packages mailman3-suite recommends:
ii  nginx-extras [nginx]  1.13.9-1

Versions of packages mailman3-suite suggests:
ii  mariadb-server-10.1 [virtual-mysql-server]  1:10.1.29-6
ii  postgresql  10+190

-- Configuration Files:
/etc/cron.d/mailman3-suite changed:
* * * * *   listcommand -v django-admin >/dev/null && django-admin 
runjobs minutely --pythonpath /usr/share/mailman3-suite --settings settings
2,17,32,47 * * * * root command -v django-admin >/dev/null && django-admin 
runjobs quarter_hourly --pythonpath /usr/share/mailman3-suite --settings 
settings
@hourly listcommand -v django-admin >/dev/null && django-admin 
runjobs hourly   --pythonpath /usr/share/mailman3-suite --settings settings
@daily  listcommand -v django-admin >/dev/null && django-admin 
runjobs daily--pythonpath /usr/share/mailman3-suite --settings settings
@weekly listcommand -v django-admin >/dev/null && django-admin 
runjobs weekly   --pythonpath /usr/share/mailman3-suite --settings settings
@monthlylistcommand -v django-admin >/dev/null && django-admin 
runjobs monthly  --pythonpath /usr/share/mailman3-suite --settings settings
@yearly listcommand -v django-admin >/dev/null && django-admin 
runjobs yearly   --pythonpath /usr/share/mailman3-suite --settings settings

/etc/logrotate.d/mailman3-suite changed:
/var/log/mailman3/mailman-suite.log {
copytruncate
daily
rotate 5
compress
delaycompress
missingok
notifempty
su www-data list
create 660 www-data list
}
/var/log/mailman3/mailman-suite-uwsgi.log {
copytruncate
weekly
rotate 3
compress
delaycompress
missingok
notifempty
su www-data list
create 660 www-data list
}


-- debconf information excluded

Bug#889515: Review of persepolis

[Moein Alinaghian]

Dear Julien,

Thanks for reviewing my package. It was really helpful.
I fixed some of the mentioned issues and uploaded a new package to
mentors.debian.net.

There are still the following issues which I cannot fix:
no-upstream-changelog - Because there isn't any upstream changelog.
debian-watch-may-check-gpg-signature - Because the upstream files are
not signed.
testsuite-autopkgtest-missing - Because there isn't a suitable test in
the upstream at the moment.

--
Sincerely yours,
Moein Alinaghian


On Sat, 24 Feb 2018 09:29:04 +0100 Julien Puydt
 wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Control: tags -1 moreinfo
>
> Hi,
>
> I had a look at your packaging, and found the following:
>
> (-) debhelper 10 -- some advise 11
> (-) standard-version 4.1.2 -- we're now at 4.1.3
> (-) in d/copyright, you could share the license chunks:
> Files: foo
> Copyright: whatever
> License: GPL-3+
>
> Files: bar
> Copyright: whatever
> License: GPL-3+
>
> License: GPL-3+
>  Here comes the text, once!
>
>
> Then I tried to compile it, and saw what lintian had to say:
>
> $ lintian -I persepolis_3.0.1-1_amd64.changes --pedantic
> P: persepolis source: package-uses-old-debhelper-compat-version 10
> (see above: should fix)
> W: persepolis source: dep5-copyright-license-name-not-unique
> (paragraph at line 26)
> (see above: must fix)
> I: persepolis source: out-of-date-standards-version 4.1.2 (released
> 2017-11-30) (current is 4.1.3)
> (see above: should fix)
> I: persepolis source: testsuite-autopkgtest-missing
> (ok, it's not always possible)
> P: persepolis source: debian-watch-does-not-check-gpg-signature
> (ok, it's not always possible)
> P: persepolis: no-upstream-changelog
> (ok, it's not always possible)
> I: persepolis: extended-description-is-probably-too-short
> (should fix)
>
> I hope that helps,
>
> Snark on #debian-mentors
> -BEGIN PGP SIGNATURE-
>
> iQIzBAEBCgAdFiEEgS7v2KP7pKzk3xFLBMU71/4DBVEFAlqRIkkACgkQBMU71/4D
> BVGnNBAAmVMhKSXnaJGGE/EdRecoVJ+Jj2hufZHlXA9hW9jY3DlDxQLv9rANl2Pg
> lH+SPv4XDMOz92A698kfAE7tQkWpnOnirvvn+En6wT971WhL93IuFtjk4qWzo/8Y
> H4DdsrCBV777VGFpflX0aq2E0FBM9hk1BeUjrNiFrMTdUmwZPglDU7Mws3swVH7R
> jSh5ZDACh0NT20mYzr8VsLkDT4m184pRTOfn0ez0ND8HtfTun3g83KYMezXmhPye
> u7cFvCcjxOkhqLQv2OoPZrHd/c0WpZzJ5zFPw3chvCMiteaEzdspoZ1coOdF1CKE
> Jh+/mD1Kjdo00D4OsHD9ReOO+olKYPTz8mKlpezZJqA7yDmSWbMMsFEPJ322q5dG
> fD/GLDbsLBjqUXoCDU185ZfSz7dol58U00fqOwMmlXzP16q4iCxTf2wisMTLlJCx
> zxsDOokRshCmqT6T4mClfA1eblSxJAqQeqTBenfroa2N0HxDAvq8jRAw9GJy6RZF
> AmYY2/D+L+zhe3dD4xs2QgKlBkMlH2kR/8/ymRoDcfCk7bZpWdvL5yBSxjVNrIFu
> 1yhXjrqMUEO72xXDVTM+JvOZ/XBifWFgEq71GvQ27k/riAsWGNP1sLQgDkzRtlj6

Bug#891702: make-guile: Please add version to Provides

[James McCoy]

Package: make-guile
Version: 4.2.1-1
Severity: normal
Tags: patch

debhelper recently added "Depends: make (>= 4~)" so that it can use
make's -O switch.  If someone has make-guile installed, rather than
make, they will currently be unable to upgrade debhelper, since
make-guile Provides/Conflicts/Replaces make but doesn't use a versioned
Provides.  Therefore, it can't satisfy a versioned Depends.

The attached patch causes make-guile to "Provides: make (=
${source:Version})" so that it can satisfy versioned Depends.

-- 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.15.0-1-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: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages make-guile depends on:
ii  guile-2.0-libs  2.0.13+1-5
ii  libc6   2.26-6
ii  libgc1c21:7.4.2-8.1

make-guile recommends no packages.

Versions of packages make-guile suggests:
pn  make-doc  
diff --git i/debian/control w/debian/control
index 04aad43..f53b48d 100644
--- i/debian/control
+++ w/debian/control
@@ -33,7 +33,7 @@ Package: make-guile
 Suggests: make-doc
 Priority: extra
 Conflicts: make
-Provides: make
+Provides: make (= ${source:Version})
 Replaces: make
 Architecture: any
 Multi-Arch: allowed

Bug#890543: on_ac_power works as documented

[Adam Borowski]

In bug #890543, you wrote:
> On a workstation system, on_ac_power gives 255 as exit code because it
> was unable to determine the power source.

The man page says:
# EXIT STATUS
#   0 (true)  System is on mains power
#   1 (false) System is not on mains power
#   255 (false)Power status could not be determined

so 255 on a desktop is expected.  There's nothing that would tell the system
where its power comes from.  (Unless you have an UPS and connect its control
link.)

It's the correct answer: the kernel can't tell a desktop from a laptop with
a battery with no supported driver.

> This would in turn make git think the system is on battery, and refuse
> to automatically perform garbage collection.

Then it's a bug in git.

The only reference to on_ac_power I see is contrib/hooks/pre-auto-gc-battery
which takes any non-zero result as "on battery".  You're right that on a
machine with no relevant sensor, garbage collection should still run.

> The proposed patch will tell the caller that AC power is present when
> there is no battery.

The patch would cause a regression: it would fold current three-state answer
into two-state, and there are use cases where "unknown" is not same as
"mains".

Instead, let's patch this in git.git.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢠⠒⠀⣿⡁ A dumb species has no way to open a tuna can.
⢿⡄⠘⠷⠚⠋⠀ A smart species invents a can opener.
⠈⠳⣄ A master species delegates.

Bug#885037: monster-masher: Please don't (Build-)Depend on gconfmm2.6

[Jeremy Bicha]

monster-masher is one of the last two packages in Debian unstable
depending on esound. (And even if that were fixed, monster-masher
depends on several other GNOME2 libraries that are being removed.)

monster-masher has been unmaintained usptream for 9 years.

https://git.gnome.org/browse/monster-masher/log/

Maybe it's time for monster-masher to be removed from Debian?

Thanks,
Jeremy Bicha

Bug#891701: Intent to file removal bug for synaesthesia

[Jeremy Bicha]

Package: synaesthesia
Version:  2.4-5.1
Severity: serious
Tags: buster sid

The Debian GNOME Team is trying to remove esound from Debian and synaesthesia
is one of the last blockers. We provided a patch in the RC bug but it
has not been applied. synaesthesia appears to be unmaintained and has
low popcon.

Please let us know if it is ok for us to file a removal bug for
synaesthesia. If we don't hear from you soon, we intend to file the
removal bug anyway.

See https://bugs.debian.org/856090

Thanks,
Jeremy Bicha

Bug#891381: vt100 line-drawing is a bad idea here

[Paul Wise]

On Tue, 2018-02-27 at 10:11 -0500, Antoine Beaupré wrote:

> ky, i'll fix the damn thing. :)

Thanks :)

> in the meantime, you can apply this on top of 1.2.0.

Huh, did not know it was possible to insert attachments in the middle
of a mail body...

> not sure i want to roll yet another trivial release just for this, do
> you mind if i wait for other/more bug reports first?

No worries, I don't intend to use it outside the terminal anyway,
was just arguing for correctness :)

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#891700: Intent to file removal bug for ll-scope

[Jeremy Bicha]

Package: ll-scope
Version: 0.2.1-3
Severity: serious
Tags: buster sid
X-Debbugs-CC: fr...@debian.org, ales...@debian.org

ll-scope appears to be unmaintained for several years. The Debian
GNOME Team is trying to remove libglademm2.4 from Debian and ll-scope
is one of the last blockers. Please let me know if it is ok for me to
file a removal bug for ll-scope.

If I don't hear from you soon, I intend to file the removal bug anyway.

See https://bugs.debian.org/885077

Thanks,
Jeremy Bicha

Bug#891698: apmd: daemon never starts (apm_available is hardcoded to no)

[Adam Borowski]

Package: apmd
Version: 3.2.2-15+b2
Severity: grave
Justification: renders package unusable

Hi!
The daemon's init script has the following line:
apm_available || exit 0
which makes it always silently fail, as apm_available contains:

.--
#!/bin/sh -e

if [ "$@" ]; then
  echo "Usage: $0"
  exit 2
fi

# APM support was removed from kernel 2.6.40 in 2011.
exit 1
`

The comment is untrue:
[/tmp/linux-4.15.4/debian]$ sgrep APM
./config/i386/config:CONFIG_APM=m
./config/armhf/config:CONFIG_APM_EMULATION=y

but regardless whether APM still works or not, the daemon will not.


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

Kernel: Linux 4.16.0-rc3-debug-00028-gf63d823da681 (SMP w/6 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages apmd depends on:
ii  debconf [debconf-2.0]  1.5.65
ii  libapm13.2.2-15+b2
ii  libc6  2.26-6
ii  lsb-base   9.20170808
ii  powermgmt-base 1.31+nmu1

apmd recommends no packages.

Versions of packages apmd suggests:
ii  xapm  3.2.2-15+b2

-- no debconf information

Bug#891699: RM: referencer -- RoQA; unmaintained; depends on unmaintained gconfmm2.6

[Jeremy Bicha]

Package: ftp.debian.org
X-Debbugs-Cc: g...@packages.debian.org

Please remove referencer from Debian.

It was orphaned in 2016. It was removed from Testing over a month ago
because it depends on gconfmm2.6 which the Debian GNOME Team is trying
to remove from Debian. Its last upstream release was 4 years ago.

https://bugs.debian.org/830812 Orphaned
https://bugs.debian.org/885039 RC bug

Thanks,
Jeremy Bicha

Bug#891697: octave-ltfat: FTBFS w/old Java (on hppa)

[Aaron M. Ucko]

Source: octave-ltfat
Version: 2.2.0+dfsg-7
Severity: important
Justification: fails to build from source (but built successfully in the past)
User: debian-h...@lists.debian.org
Usertags: hppa

Builds of octave-ltfat for hppa [1] (admittedly not a release
architecture) have been failing lately with numerous errors (and even
more warnings) trying to build under inst/blockproc/java.  hppa is
noteworthy for having an outdated default-jdk package.  (So is
hurd-i386, but octave itself is too old there at present.)

The fact that this error showed up between 2.2.0+dfsg-4 and
2.2.0+dfsg-7 suggests that it may be possible to do without this Java
code.  However, if it really is necessary nowadays, please version the
build dependency on default-jdk to (>= 2:1.8~), noting the epoch.

Thanks!

[1] 
https://buildd.debian.org/status/fetch.php?pkg=octave-ltfat=hppa=2.2.0%2Bdfsg-7=1518890201=0

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#888509: Acknowledgement (BUG: soft lockup - CPU# stuck)

[Christoph Anton Mitterer]

There is some indication, that this issue doesn't occur with the kernel
from oldstable (i.e. 3.16.51-3+deb8u1, with the rest of our userland
still at stretch)... at least we have on node downgraded to that
kernel, and so far that one wasn't hit in nearly two weeks, while many
other were.

If there's anything you'd need in terms of data/debug output, etc. do
not hesitate to ask.

Thanks,
Chris.

Bug#891696: miniupnpc: FTBFS on non-Linux: Cannot find miniupnpc.3.gz

[Aaron M. Ucko]

Source: miniupnpc
Version: 2.0.20171212-3
Severity: normal
User: debian-h...@lists.debian.org
Usertags: hurd

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

 dh_install -a -O--buildsystem=makefile
  dh_install: Cannot find (any matches for) "usr/share/man/man3/miniupnpc.3.gz" 
(tried in ., debian/tmp)
  
  dh_install: libminiupnpc-dev missing files: usr/share/man/man3/miniupnpc.3.gz
  dh_install: missing files, aborting
  debian/rules:12: recipe for target 'binary-arch' failed
  make: *** [binary-arch] Error 2

The issue appears to be that the upstream makefile conditionally
compresses this manpage [1], whereas libminiupnpc.install specifically
expects it to be compressed.  (As such, builds for kFreeBSD would fail
in the same fashion if and when they ever come back.) You might consider
using a wildcard in the install file (.../miniupnpc.3*) and letting
dh_compress take care of compression as needed.

Could you please take a look?

Thanks!

[1] https://sources.debian.org/src/miniupnpc/2.0.20171212-3/Makefile/#L254

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#891610: why? It works.

[Adam Borowski]

> Please stop suggesting powermgmt-base: this is an obsolete, orphaned and
> unmantained package which I last NMU'ed myself in 2014.

No maintenance is needed there -- kernel interface hasn't changed in a long
long time.  I just took a look at the package, and didn't find anything
worth the effort to improve: you can slightly optimize tests ([ -d dir ] &&
[ -d dir/subdir ] is redundant), bump standards version/etc, and that's it.

At the first glance, it is tempting to drop support for ancient interfaces
like APM or PMU, but RTFKing, I see that the only PMU driver
(drivers/macintosh/via-pmu.c) doesn't register itself in sysfs.  That driver
is used only for Apple Powermacs, which are a platform not exactly likely to
see lively development, but are still supported by current unstable.

Thus, 99.99% machines will use the modern sysfs interface, while stragglers
keep working.  Which can't be said about systemd, which doesn't support PMU.

> It provides the on_ac_power command which is only used on non-systemd 
> systems anyway.

Newsflash: not everyone suffers from systemd -- either by choice or by
systemd not supporting people's hardware or use cases.  One example are the
aforemented Apple Powermacs (ancient), another are both laptops I own, the
newer of which was released in April 2017.

powermgmt-base's on_ac_power knows about all interfaces provided by Linux,
systemd's equivalent does not.  Thus, it's clearly better to use the former.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢠⠒⠀⣿⡁ A dumb species has no way to open a tuna can.
⢿⡄⠘⠷⠚⠋⠀ A smart species invents a can opener.
⠈⠳⣄ A master species delegates.

Bug#891695: "mh_linkjar" and "mh_installpoms" Do Not Support "--relocate"

[殷啟聰 | Kai-Chung Yan]

Package: maven-repo-helper
Version: 1.9.2
Severity: important

If I use "jh_maven_repo_helper" and then add a "relocate" option to 
".poms", "mh_linkjar" shows the following error:

> Invalid option: relocate

So I move the "relocate" option to "debian/rules" as

```make
override_mh_installpoms:
    mh_installpoms --relocate=org.osgi:org.osgi.compendium:debian
``

This time, "mh_installpoms" shows said error.

FYI: I was updating "osgi-compendium" to release 6 which renames itself to 
"osgi.cmpn.jar".



signature.asc
Description: OpenPGP digital signature

Bug#891553: [Pkg-mailman-hackers] Bug#891553: mailman3-suite: Cannot remove package

[Colin Turner]

Hi Jonas,

> Am 26.02.2018 um 17:01 schrieb Colin Turner:
>> Thanks for your work on this package.
> 
> Thanks for reporting the bug :)

Thanks for the rapid reply!

>> I attempted to install mailman3 but found that the service would not start 
>> and generated a lot of cron errors as a result. Efforts to configure and fix 
>> the package failed and I decided to remove it.
> 
> Mh, could you report the issues you discovered with starting mailman3 in
> separate bugreports? Is it mailman3-core that fails to start, or the
> UWSGI daemon in mailman3-suite? What's the exact "cron errors" you get?

I’ve removed the package with your instructions below. Many thanks. I’ve tried 
to reinstall and will file separate bugs. (I hope, I’ve had to reconfigure the 
mail server on the machine I was testing on as it is not no longer in actual 
service).

Kind regards,

CT.

Bug#884514: ruby-fog-aws: fails to upgrade from 'sid' - trying to overwrite /usr/lib/ruby/vendor_ruby/fog/aws/service_mapper.rb

[Andreas Beckmann]

Followup-For: Bug #884514
Control: reopen -1
Control: affects -1 + ruby-fog

No longer shipping the file in ruby-fog is only half of the fix. Now
ruby-fog-aws still needs Breaks+Replaces: ruby-fog (<< 1.42.0).


Andreas

Bug#849812: Info received (Bug#849812: ITP: requests-ntlm -- HTTP NTLM authentication using the requests library)

[Harlan Lieberman-Berg]

forwarded 849812 https://github.com/jborean93/ntlm-auth/issues/19
thanks

Looks like this is blocked because of copyright issues again; this time,
incompatibility between GPLv2 and LGPLv3+.

On hold again for now.

On Tue, Feb 27, 2018 at 9:03 PM, Debian Bug Tracking System <
ow...@bugs.debian.org> 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):
>  w...@debian.org
>  Dominic Hargreaves 
>
> If you wish to submit further information on this problem, please
> send it to 849...@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.
>
> --
> 849812: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849812
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>



-- 
Harlan Lieberman-Berg
~hlieberman

Bug#891663: [pkg-gnupg-maint] Bug#891663: [PATCH] libgpg-error: Add support for the riscv64 architecture

[NIIBE Yutaka]

Hello,

Thanks for your report.

Karsten Merker  wrote:
> AIUI, libgpg-error requires a per-architecture header file
> "src/syscfg/lock-obj-pub..h", which upstream doesn't
> provide for riscv64.

As upstream, the change is pushed by the commit: 596c0d7
-- 

Bug#891694: python3-murano: mentions Python 2.x in the package description

[Paul Wise]

Package: python3-murano
Version: 1:5.0.0~rc2-1
Severity: minor

Python 2.x is mentioned in the package description
but the package only contains code for Python 3:

$ apt-cache show python3-murano | grep Python
Description-en: cloud-ready application catalog - Python 2.x server code
 This package contains the Python 2.x server code.
$ apt-file show python3-murano | grep python2
$ apt-file show python3-murano | head -n1
python3-murano: 
/usr/lib/python3/dist-packages/murano-5.0.0.0rc2.egg-info/PKG-INFO

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

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

Versions of packages python3-murano depends on:
pn  alembic 
ii  python3 3.6.4-1
pn  python3-alembic 
ii  python3-babel   2.4.0+dfsg.1-2
pn  python3-castellan   
pn  python3-congressclient  
ii  python3-cryptography2.1.4-1
pn  python3-debtcollector   
pn  python3-eventlet
pn  python3-heatclient  
pn  python3-jsonpatch   
pn  python3-jsonschema  
pn  python3-keystoneauth1   
pn  python3-keystoneclient  
pn  python3-keystonemiddleware  
pn  python3-kombu   
pn  python3-mistralclient   
pn  python3-muranoclient
pn  python3-mysqldb 
pn  python3-netaddr 
pn  python3-neutronclient   
pn  python3-oslo.concurrency
pn  python3-oslo.config 
pn  python3-oslo.context
pn  python3-oslo.db 
pn  python3-oslo.i18n   
pn  python3-oslo.log
pn  python3-oslo.messaging  
pn  python3-oslo.middleware 
pn  python3-oslo.policy 
pn  python3-oslo.serialization  
pn  python3-oslo.service
pn  python3-oslo.utils  
pn  python3-paste   
pn  python3-pastedeploy 
ii  python3-pbr 3.1.1-4
ii  python3-psutil  5.4.2-1
ii  python3-psycopg22.7.4-1
pn  python3-pymysql 
ii  python3-requests2.18.4-2
pn  python3-routes  
pn  python3-semantic-version
ii  python3-six 1.11.0-2
pn  python3-sqlalchemy  
ii  python3-stevedore   1.25.0-2
pn  python3-tenacity
pn  python3-testtools   
ii  python3-webob   1:1.7.3-2
ii  python3-yaml3.12-1+b1
pn  python3-yaql

Versions of packages python3-murano recommends:
pn  python3-ldap  

python3-murano suggests no packages.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#891693: rakudo: fails to upgrade from 'testing' - trying to overwrite /usr/lib/perl6/runtime/dynext/libperl6_ops_moar.so

[Andreas Beckmann]

Package: rakudo
Version: 2018.02.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Preparing to unpack .../rakudo_2018.02.1-1_amd64.deb ...
  Unpacking rakudo (2018.02.1-1) over (2017.06-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/rakudo_2018.02.1-1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/perl6/runtime/dynext/libperl6_ops_moar.so', 
which is also in package rakudo-lib 2017.06-1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/rakudo_2018.02.1-1_amd64.deb


cheers,

Andreas


rakudo_2018.02.1-1.log.gz
Description: application/gzip

Bug#890878: RFS: company-irony

[Nicholas D Steeves]

On Mon, Feb 26, 2018 at 02:43:51PM -0700, Sean Whitton wrote:
> Hello,
> 
> On Mon, Feb 26 2018, Alberto Luaces wrote:
> 
> > I have refreshed those fields.  I have not still refreshed the
> > changelog date in order to wait for more potential changes.
> 
> Thanks for fixing this.
> 
> I'm not in a position to properly review this package, unfortunately.
> Sorry for suggesting in a previous mail that I was planning on doing
> that.  Just wanted to get the Vcs-* fields fixed.
> 
> -- 
> Sean Whitton

Hi Alberto,

Welcome to the team, and thank you for packaging company-irony!  I
consider it a valuable addition to the archive :-)  The following
might be something you already know, but if not, here's a neat trick:

Make your changes, and then while in emacs, M-x magit-status, then d u
(diff unstaged).  Stage the changes that are part of one logical
operation with C-, select region, then s (or just s on a hunk to
stage the whole hunk).  Finally c c (commit staged), write your commit
message, and finally C-c C-c.  Later you can use gbp dch -a [-N
$upstream_version-$debian_revision, if necessary] to generate a nice changelog.

Hi Sean and David,

I'm willing to do reviews, and want to encourage best practises and our
team's high standards.  Please feel free to comment.

debian/copyright:
  Author's email is directly underneath Copyright in
  company-irony.el's header.  I would either Add it to the Copyright:
  for the 'Files: *' section, or add an Upstream-Contact field. (
  https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/#examples
  ) Sean, what's your best practices stance on this?  I'm guessing
  Upstream-Contact.

debian/gbp.conf:
  gbp:info: Tarballs 'company-irony_1.1.0.orig.tar.xz' not found
  gbp:warning: Pristine-tar branch "pristine-tar" not found
  gbp:info: Creating
  /home/sten/devel/build-area/company-irony_1.1.0.orig.tar.xz
  gbp:error: v1.1.0 is not a valid treeish

  Alberto, if you're using pristine-tar you need to push the branch;
  alternatively, if you got upstream source from git and are not using
  pristine-tar you need to push the upstream tag to our repo and also
  modify gbp.conf to indicate you're not using pristine-tar.  Also,
  for future reference, if you choose the git-only workflow you'll
  need to push each new upstream version tag as you update the
  package.

debian/watch:
  Missing, please add one.  Between the one for irony-mode (watch
  version 3, Guillaume is also the upstream for this one) and
  fountain-mode (version 4) you should be able to figure out how to
  produce a working v4 one ;-)  The only reason I mention
  fountain-mode is because it's the one I've checked most recently.

I'll do a more in depth review in the next round.

Cheers,
Nicholas


signature.asc
Description: PGP signature

Bug#891692: ITP

[Harlan Lieberman-Berg]

Package: wnpp
Severity: wishlist

From: Harlan Lieberman-Berg 
To: Debian Bug Tracking System 
Subject: ITP: python-ntlm-auth -- NTLM low-level python library
X-Debbugs-CC: Harlan Lieberman-Berg , 
debian-de...@lists.debian.org
Date: Tue, 27 Feb 2018 21:05:41 -0500
Message-ID: 
<87a7vtvpfu.fsf@aztlan.i-did-not-set--mail-host-address--so-tickle-me>
--text follows this line--
Package: wnpp
Owner: Harlan Lieberman-Berg 
Severity: wishlist

* Package name: python-ntlm-auth
  Version : 1.0.6
  Upstream Author : Jordan Borean 
* URL or Web page : https://github.com/jborean93/ntlm-auth
* License : LGPLv3+
  Description : NTLM low-level python library

  This library handles the low-level details of NTLM authentication for
  use in authenticating with a service that uses NTLM. It will create
  and parse the 3 different message types in the order required and
  produce a base64 encoded value that can be attached to the HTTP
  header.

  The goal of this library is to offer full NTLM support including
  signing and sealing of messages as well as supporting MIC for message
  integrity and the ability to customise and set limits on the messages
  sent.

  It is primarily packaged as a dependency for the user-facing library,
  requests-ntlm.

Bug#849812: ITP: requests-ntlm -- HTTP NTLM authentication using the requests library

[Harlan Lieberman-Berg]

owner 849812 !
thanks

Sounds good, Dominic!  I'll move this forward through DPMT.

Sincerely,

On Tue, Feb 27, 2018 at 12:13 PM, Dominic Hargreaves  wrote:
> On Mon, Feb 26, 2018 at 10:58:03PM -0500, Harlan Lieberman-Berg wrote:
>> On Fri, 25 Aug 2017 15:37:42 +0100 Dominic Hargreaves  wrote:
>> > After a bit of delay I worked on this, to discover that its depedency
>> > ntlm-auth had no copyright statement. I am awaiting clarification
>> > from upstream on that:
>> >
>> > .
>>
>> Hi Dom,
>>
>> Just had an ansible user ping me about this (because of the transitive
>> dep from winrm).  Is this something you're still in the midst of
>> packaging, and/or is there anything I can do to help?
>
> Hello,
>
> I'm afraid this work has entirely stalled as I don't have a current
> need for this module, although upstream did fix the copyright notice.
> If you would like to take on packaging ntlm-auth/updating pywinrm
> within the python packaging team that'd be great. Otherwise, I will
> get to it eventually...
>
> Best,
> Dominic.



-- 
Harlan Lieberman-Berg
~hlieberman

Bug#891691: mailman3-core: Cannot install mailman3-suite with mysql database

[Colin Turner]

Package: mailman3-core
Version: 3.1.1-4
Severity: normal

Dear Maintainer,

Many thanks for your work on these packages. I'm following up from bug 891553.

I have attempted to install mailman3-suite, and allowed automatic configuration 
using mysql. I think this was the default presented choice.
This configuration failed, with this error transcript.

Errors were encountered while processing:
 mailman3-suite
E: Sub-process /usr/bin/dpkg returned an error code (1)
Setting up mailman3-suite (0+20170523-10) ...
Determining localhost credentials from /etc/mysql/debian.cnf: succeeded.
dbconfig-common: writing config to /etc/dbconfig-common/mailman3-suite.conf
mailman3suite already exists and has privileges on mailman3suite.
creating database mailman3suite: already exists.
dbconfig-common: flushing administrative password
Traceback (most recent call last):
  File "/usr/bin/django-admin", line 21, in 
management.execute_from_command_line()
  File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", 
line 364, in execute_from_command_line
utility.execute()
  File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", 
line 338, in execute
django.setup()
  File "/usr/lib/python2.7/dist-packages/django/__init__.py", line 27, in setup
apps.populate(settings.INSTALLED_APPS)
  File "/usr/lib/python2.7/dist-packages/django/apps/registry.py", line 108, in 
populate
app_config.import_models()
  File "/usr/lib/python2.7/dist-packages/django/apps/config.py", line 202, in 
import_models
self.models_module = import_module(models_module_name)
  File "/usr/lib/python2.7/importlib/__init__.py", line 37, in import_module
__import__(name)
  File "/usr/lib/python2.7/dist-packages/hyperkitty/models/__init__.py", line 
27, in 
from .category import ThreadCategoryg
  File "/usr/lib/python2.7/dist-packages/hyperkitty/models/category.py", line 
30, in 
class ThreadCategory(models.Model):
  File "/usr/lib/python2.7/dist-packages/django/db/models/base.py", line 124, 
in __new__
new_class.add_to_class('_meta', Options(meta, app_label))
  File "/usr/lib/python2.7/dist-packages/django/db/models/base.py", line 325, 
in add_to_class
value.contribute_to_class(cls, name)
  File "/usr/lib/python2.7/dist-packages/django/db/models/options.py", line 
214, in contribute_to_class
self.db_table = truncate_name(self.db_table, 
connection.ops.max_name_length())
  File "/usr/lib/python2.7/dist-packages/django/db/__init__.py", line 33, in 
__getattr__
return getattr(connections[DEFAULT_DB_ALIAS], item)
  File "/usr/lib/python2.7/dist-packages/django/db/utils.py", line 211, in 
__getitem__
backend = load_backend(db['ENGINE'])
  File "/usr/lib/python2.7/dist-packages/django/db/utils.py", line 115, in 
load_backend
return import_module('%s.base' % backend_name)
  File "/usr/lib/python2.7/importlib/__init__.py", line 37, in import_module
__import__(name)
  File "/usr/lib/python2.7/dist-packages/django/db/backends/mysql/base.py", 
line 30, in 
'Did you install mysqlclient or MySQL-python?' % e
django.core.exceptions.ImproperlyConfigured: Error loading MySQLdb module: No 
module named MySQLdb.
Did you install mysqlclient or MySQL-python?
dpkg: error processing package mailman3-suite (--configure):
 installed mailman3-suite package post-installation script subprocess returned 
error exit status 1
Errors were encountered while processing:
 mailman3-suite

So I'm guessing there is a missing dependency here. I tried installing 
python-mysqldb, but this provided a different error:

Errors were encountered while processing:
 mailman3-suite
E: Sub-process /usr/bin/dpkg returned an error code (1)
Setting up mailman3-suite (0+20170523-10) ...
Determining localhost credentials from /etc/mysql/debian.cnf: succeeded.
dbconfig-common: writing config to /etc/dbconfig-common/mailman3-suite.conf
mailman3suite already exists and has privileges on mailman3suite.
creating database mailman3suite: already exists.
dbconfig-common: flushing administrative password
Traceback (most recent call last):
  File "/usr/bin/django-admin", line 21, in 
management.execute_from_command_line()
  File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", 
line 364, in execute_from_command_line
utility.execute()
  File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", 
line 356, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 
283, in run_from_argv
self.execute(*args, **cmd_options)
  File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 
330, in execute
output = self.handle(*args, **options)
  File 
"/usr/lib/python2.7/dist-packages/django/core/management/commands/migrate.py", 
line 204, in handle
fake_initial=fake_initial,
  File "/usr/lib/python2.7/dist-packages/django/db/migrations/executor.py", 
line 115, in 

Bug#891674: Patch to fix the problem

[Peter.Chubb]

The linux kernel treats PCI domains as 32 bit ints.

diff -ru libpciaccess-0.13.4/include/pciaccess.h 
libpciaccess-0.13.4-fixed/include/pciaccess.h
--- libpciaccess-0.13.4/include/pciaccess.h 2015-05-01 14:44:47.0 
+1000
+++ libpciaccess-0.13.4-fixed/include/pciaccess.h   2018-02-28 
12:21:12.280963252 +1100
@@ -321,7 +321,7 @@
  * the domain will always be zero.
  */
 /*@{*/
-uint16_tdomain;
+uint32_tdomain;
 uint8_t bus;
 uint8_t dev;
 uint8_t func;
diff -ru libpciaccess-0.13.4/src/linux_sysfs.c 
libpciaccess-0.13.4-fixed/src/linux_sysfs.c
--- libpciaccess-0.13.4/src/linux_sysfs.c   2015-05-01 14:44:47.0 
+1000
+++ libpciaccess-0.13.4-fixed/src/linux_sysfs.c 2018-02-28 12:21:32.676941130 
+1100
@@ -157,7 +157,7 @@
(struct pci_device_private *) >devices[i];
 
 
-   sscanf(devices[i]->d_name, "%04x:%02x:%02x.%1u",
+   sscanf(devices[i]->d_name, "%x:%02x:%02x.%1u",
   & dom, & bus, & dev, & func);
 
device->base.domain = dom;

-- 
Dr Peter Chubb Tel: +61 2 9490 5852  http://ts.data61.csiro.au/
Trustworthy Systems Group   Data61 (formerly NICTA)

Bug#891674: More info

[Peter.Chubb]

I built Xorg from source so I could get debugging symbols.

The crash is in  xf86VGAarbiterInit(), when it calls
pci_device_vgaarb_init().  This function can read /dev/vga_arbiter
which ordinary users cannot.

# head -1 < /dev/vga_arbiter 
count:1,PCI::65:00.0,decodes=io+mem,owns=none,locks=none(0:0)

pci_sys->devices is null.

The problem appears to be a bad scan format in
line 160 of linux_sysfs.c
   sscanf(devices[i]->d_name, "%04x:%02x:%02x.%1u",

ls /sys/bus/pci/devices shows devices with a BUS > 0x taking 5
digits.


ls /sys/bus/pci/devices
:00:00.0  :00:1f.2  :16:0e.4  :64:09.0  :64:0d.1
:00:04.0  :00:1f.3  :16:0e.5  :64:0a.0  :64:0d.2
:00:04.1  :00:1f.4  :16:0e.6  :64:0a.1  :64:0d.3
:00:04.2  :00:1f.6  :16:0e.7  :64:0a.2  :65:00.0
:00:04.3  :02:00.0  :16:0f.0  :64:0a.3  :65:00.1
:00:04.4  :16:05.0  :16:0f.1  :64:0a.4  :b2:05.0
:00:04.5  :16:05.2  :16:1d.0  :64:0a.5  :b2:05.2
:00:04.6  :16:05.4  :16:1d.1  :64:0a.6  :b2:05.4
:00:04.7  :16:08.0  :16:1d.2  :64:0a.7  :b2:05.5
:00:05.0  :16:08.1  :16:1d.3  :64:0b.0  :b2:12.0
:00:05.2  :16:08.2  :16:1e.0  :64:0b.1  :b2:12.1
:00:05.4  :16:08.3  :16:1e.1  :64:0b.2  :b2:12.2
:00:08.0  :16:08.4  :16:1e.2  :64:0b.3  :b2:15.0
:00:08.1  :16:08.5  :16:1e.3  :64:0c.0  :b2:16.0
:00:08.2  :16:08.6  :16:1e.4  :64:0c.1  :b2:16.4
:00:14.0  :16:08.7  :16:1e.5  :64:0c.2  :b2:17.0
:00:14.2  :16:09.0  :16:1e.6  :64:0c.3  1:00:02.0
:00:16.0  :16:09.1  :64:00.0  :64:0c.4  1:00:03.0
:00:17.0  :16:0e.0  :64:05.0  :64:0c.5  1:01:00.0
:00:1c.0  :16:0e.1  :64:05.2  :64:0c.6
:00:1c.6  :16:0e.2  :64:05.4  :64:0c.7
:00:1f.0  :16:0e.3  :64:08.0  :64:0d.0



-- 
Dr Peter Chubb Tel: +61 2 9490 5852  http://ts.data61.csiro.au/
Trustworthy Systems Group   Data61 (formerly NICTA)

Bug#891687: another alternative approach

[Daniel Kahn Gillmor]

the approach in the attached patch offers a different user-owned cluster
*per instantiated template*.

This keeps the data for each invoked database localized, within that
named directory in ~/.config/foo.

Another approach would be to have a single
/usr/lib/systemd/user/postgresql.service that runs a single cluster
(under ~/.config/postgresql/ perhaps?), and to have some separate
templated unit that would create a database in that cluster.

This makes the per-application backup story slightly more complicated,
but it's still not too bad.

If that approach sounds like something you'd be more likely to accept,
i'm happy to send a patch implementing it.

let me know if you have any suggestions, criticisms, or feedback!

Regards,

--dkg

Bug#891689: Multi-arch support is incomplete

[Gunnar Hjalmarsson]

Debdiff attached.

--
Gunnar Hjalmarsson
https://launchpad.net/~gunnarhj
diff -ru libsidplay-1.36.59.orig/debian/changelog 
libsidplay-1.36.59/debian/changelog
--- libsidplay-1.36.59.orig/debian/changelog2016-09-06 19:00:07.0 
+0200
+++ libsidplay-1.36.59/debian/changelog 2018-02-28 02:25:03.254669829 +0100
@@ -1,3 +1,10 @@
+libsidplay (1.36.59-11) unstable; urgency=low
+
+  * debian/control:
+- Build with "Multi-Arch: same" (closes: #891689, LP: #1621861).
+
+ -- Gunnar Hjalmarsson   Wed, 28 Feb 2018 02:25:00 +0100
+
 libsidplay (1.36.59-10) unstable; urgency=low
 
   [ Helmut Grohne  ]
diff -ru libsidplay-1.36.59.orig/debian/control 
libsidplay-1.36.59/debian/control
--- libsidplay-1.36.59.orig/debian/control  2016-07-16 00:32:35.0 
+0200
+++ libsidplay-1.36.59/debian/control   2018-02-27 23:49:56.671698477 +0100
@@ -8,6 +8,7 @@
 Package: libsidplay1v5
 Section: libs
 Architecture: any
+Multi-Arch: same
 Depends: ${misc:Depends}, ${shlibs:Depends}
 Conflicts: libsidplay1.36, sidplay (<= 1.36.36), libsidplay1-c102 (<= 
1.36.59-2), libsidplay1
 Replaces: libsidplay1.36, libsidplay1-c102 (<= 1.36.59-2), libsidplay1
@@ -27,6 +28,7 @@
 Section: libdevel
 Priority: extra
 Architecture: any
+Multi-Arch: same
 Depends: ${misc:Depends}, libsidplay1v5 (= ${binary:Version})
 Conflicts: libsidplay1.36-dev
 Replaces: libsidplay1.36-dev

Bug#891690: libclang-common-4.0-dev: /usr/lib/llvm-4.0/lib/clang/4.0.1/lib/ is empty on mipsel

[Andreas Beckmann]

Package: libclang-common-4.0-dev
Version: 1:4.0.1-10
Severity: serious

Hi,

while analyzing this pocl failure:

https://buildd.debian.org/status/fetch.php?pkg=pocl=mipsel=1.1%7Erc2-1=1519758612=0

  /usr/bin/ld: cannot find
  
/usr/lib/llvm-4.0/bin/../lib/clang/4.0.1/lib/linux/libclang_rt.builtins-mipsel.a:
  No such file or directory

  clang: error: linker command failed with exit code 1 (use -v to see
  invocation)

I found that libclang-common-4.0-dev should contain libclang_rt.builtins-*.a
according to
https://packages.debian.org/sid/mipsel/libclang-common-4.0-dev/filelist
but the last version that actually shipped these files was 1:4.0.1-1.

libclang_rt.builtins-*.a is missing for several other architectures, too,
(the pocl build logs for these architectures mention it:
  armel, mips, mips64el, mipsel, powerpc, ppc64, ppc64el, s390x)
but I didn't dig into the details there.


Andreas

Bug#891689: Multi-arch support is incomplete

[Gunnar Hjalmarsson]

Package: src:libsidplay
Version: 1.36.59-10
Tags: patch

This is a forward of . In addition 
to the change due to , debian/control 
needs to include "Multi-Arch: same".


--
Gunnar Hjalmarsson
https://launchpad.net/~gunnarhj

Bug#891688: lintian: warn about missing Vcs-Browser field when Vcs-* mention hosts with browsable archives

[Paul Wise]

Package: lintian
Version: 2.5.76
Severity: wishlist

Some packages have a Vcs-* field but no Vcs-Browser field and are
using hosting services that support browsing the VCS tree and history.

An example of a package that should trigger this complaint is debsecan.

I would suggest that it be info level because most of the VCS services
that people use have redirects from the VCS URL to the browse URL.

Please initially detect a missing Vcs-Browser field for the following.
There are definitely more servers that support browsable archives,
but this list will be a reasonable start for this tag.

Vcs-Git: git://anonscm.debian.org/
Vcs-Git: https?://anonscm.debian.org/git/
Vcs-Git: https?://anonscm.debian.org/cgit/
Vcs-Git: git://git.debian.org/
Vcs-Git: https?://git.debian.org/
Vcs-Git: git://alioth.debian.org/
Vcs-Git: https?://alioth.debian.org/anonscm/git/
Vcs-Git: git://anongit.debian.org/
Vcs-Git: https?://git.dgit.debian.org/
Vcs-Git: git://anongit.freedesktop.org/
Vcs-Git: git://anongit.kde.org/
Vcs-Git: git://git.code.sf.net/
Vcs-Git: https?://git.code.sf.net/p/
Vcs-Git: git://*.git.sourceforge.net/
Vcs-Git: git://g...@github.com:
Vcs-Git: git://github.com/
Vcs-Git: https?://github.com/
Vcs-Git: g...@gitlab.com:
Vcs-Git: https?://gitlab.*/
Vcs-Git: https?://salsa.debian.org/
Vcs-Git: git://git.kernel.org/
Vcs-Git: git://gitorious.org/
Vcs-Git: git://*.branchable.com/
Vcs-Git: git://repo.or.cz/
Vcs-Git: https?://repo.or.cz/
Vcs-Git: https?://bitbucket.org/

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#891687: postgresql-common: dsfwew

[Daniel Kahn Gillmor]

Package: postgresql-common
Version: 190
Severity: wishlist
Tags: patch

Some user accounts might run a daemon (a "user service") that wants
its own postgresql cluster without relying on the system cluster.

For example, there are daemons that handle sensitive data that they
don't want another system account to access, or that they want to be
able to tightly control the backup schedule for.

Alternately, the system cluster might be configured and in use for a
different purpose; so the user service might not be able to easily get
access to it.

The attached patch makes it easier to support these use cases on
Debian systems that run systemd.

In particular, a user .service named "exampled" which keeps its
state in `~/.config/example`.  An `exampled.service` unit might be
configured with:

Requires=pgcluster@example.service
After=pgcluster@example.service

So that if the user service is ever started, the cluster will be
created on demand (in `~/.config/example/data`) and the "example"
database will be ready for use (via unix-domain sockets in
`$XDG_RUNTIME_DIR/example/`) before the user service is started.

Regards,

--dkg

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

Kernel: Linux 4.14.0-3-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: systemd (via /run/systemd/system)

Versions of packages postgresql-common depends on:
ii  adduser   3.117
ii  debconf [debconf-2.0] 1.5.65
ii  lsb-base  9.20170808
ii  postgresql-client-common  190
ii  procps2:3.3.12-4
ii  ssl-cert  1.0.39
ii  ucf   3.0037

Versions of packages postgresql-common recommends:
ii  e2fsprogs  1.43.9-1
ii  logrotate  3.11.0-0.1

Versions of packages postgresql-common suggests:
ii  libjson-perl  2.97001-1

-- Configuration Files:
/etc/postgresql-common/createcluster.conf changed [not included]

-- debconf information excluded
>From 6db58c09704dc61310e4dda9607afcfc9f1dab65 Mon Sep 17 00:00:00 2001
From: Daniel Kahn Gillmor 
Date: Tue, 27 Feb 2018 19:26:46 -0500
Subject: [PATCH] Implement easily-managed user clusters under systemd

Some user services might want their own local postgresql cluster.
This makes it easy for those services to spin up a dedicated cluster +
db on demand.
---
 Makefile  |   1 +
 debian/postgresql-common.install  |   3 +
 debian/postgresql-common.links|   1 +
 debian/postgresql-common.manpages |   1 +
 pgcluster@.service|   8 +++
 postgres-user-cluster |  59 ++
 psql-user-cluster |   5 ++
 psql-user-cluster.pod | 128 ++
 8 files changed, 206 insertions(+)
 create mode 100644 pgcluster@.service
 create mode 100755 postgres-user-cluster
 create mode 100755 psql-user-cluster
 create mode 100644 psql-user-cluster.pod

diff --git a/Makefile b/Makefile
index 6ee9adf..402c2ed 100644
--- a/Makefile
+++ b/Makefile
@@ -9,6 +9,7 @@ POD1PROGS = pg_conftool.1 \
pg_wrapper.1
 POD1PROGS_POD = pg_buildext.1 \
pg_virtualenv.1 \
+   psql-user-cluster.1 \
dh_make_pgxs/dh_make_pgxs.1
 POD8PROGS = pg_updatedicts.8
 
diff --git a/debian/postgresql-common.install b/debian/postgresql-common.install
index ebd0c50..caacc79 100644
--- a/debian/postgresql-common.install
+++ b/debian/postgresql-common.install
@@ -12,7 +12,10 @@ pg_renamecluster usr/bin
 pg_updatedicts usr/sbin
 pg_upgradecluster usr/bin
 pg_virtualenv usr/bin
+pgcluster@.service usr/lib/systemd/user
 pgdg usr/share/postgresql-common
+postgres-user-cluster usr/share/postgresql-common
+psql-user-cluster usr/bin
 run-upgrade-scripts usr/share/postgresql-common
 t/* usr/share/postgresql-common/t
 testsuite usr/share/postgresql-common
diff --git a/debian/postgresql-common.links b/debian/postgresql-common.links
index 2bf1bda..41d67c8 100644
--- a/debian/postgresql-common.links
+++ b/debian/postgresql-common.links
@@ -1 +1,2 @@
 usr/share/postgresql-common/pg_wrapper usr/bin/pg_archivecleanup
+usr/share/man/man1/psql-user-cluster.1 usr/share/man/man1/pgcluster@.service.1
diff --git a/debian/postgresql-common.manpages 
b/debian/postgresql-common.manpages
index 4b21c26..1778484 100644
--- a/debian/postgresql-common.manpages
+++ b/debian/postgresql-common.manpages
@@ -7,3 +7,4 @@ pg_renamecluster.1
 pg_updatedicts.8
 pg_upgradecluster.1
 pg_virtualenv.1
+psql-user-cluster.1
diff --git a/pgcluster@.service b/pgcluster@.service
new file mode 100644
index 000..a8f5a3f
--- /dev/null
+++ b/pgcluster@.service

Bug#888391: lynx: RUBOUT deletes character in FRONT of the cursor instead of BEHIND

[Thomas Dickey]

On Thu, Jan 25, 2018 at 03:04:51PM +0100, Axel Beckert wrote:
> Hi,
> 
> ank man wrote:
> > > I've tested all lynx versions available in supported Debian releases
> > > and found that those lynx versions in
> > >
> > > * Debian Unstable/Buster (2.8.9dev16-2),
> > > * Debian 9 Stretch (2.8.9dev11-1), and
> > > * Debian 8 Jessie (2.8.9dev1-2)
> > >
> > > exhibit this behaviour, but not the lynx version in
> > >
> > > * Debian 7 Wheezy (2.8.8dev.12-2).
> > 
> > And as mentioned in (an older, hasn't been updated for years) OpenBSD .

hmm - I have VMs for Debian 5-9 (and some others), but checking
Debian 6-9, I don't see the behavior described.

For clarification,

+ the large key on the qwerty main-keyboard may be
  labeled "backspace", may have an arrow, etc,
  but with Debian it sends DEL, not backspace.
+ The key labeled "Delete" does not send DEL.
  It sends an escape sequence on most terminals, e.g., ^[[3~
+ The key labeled "Del" on the numeric keypad does not send DEL.
  It sends (not surprise) an escape sequence in xterm, e.g, ^[On

(using "^[" for escape just for readability).  In the Options menu,
Lynx has choices for keyboard ("Line edit style).

Here's some data noted while editing text-fields in the options menu:

Debian  LynxKeyboardBackspace   Delete  Del

6   2.8.8dev.5-1bashDELPDELNnone
6   2.8.8dev.5-1alternate   DELPDELPnone
6   2.8.8dev.5-1default DELPDELPnone

7   2.8.8dev.12-2+deb7u2 bash   DELPDELNnone
7   2.8.8dev.12-2+deb7u2 alternate  DELPDELPnone
7   2.8.8dev.12-2+deb7u2 defaultDELPDELPnone

8   2.8.9dev1-2+deb8u1 bash DELPDELNnone
8   2.8.9dev1-2+deb8u1 alternateDELPDELPnone
8   2.8.9dev1-2+deb8u1 default  DELPDELPnone

9   2.8.9dev11-1bashDELPDELNnone
9   2.8.9dev11-1alternate   DELPDELPnone
9   2.8.9dev11-1default DELPDELPnone
 
referring to the section in lynx.cfg discussing keymap:
#  DELN # Delete next/curr char
#  DELP # Delete prev  char

and "none" indicates that the escape sequence from xterm's keypad is ignored.

If you use the "-cmd_log" option to record the keystrokes, those
"Backspace" and "Delete" keys should show as
key 
key Remove key

in xterm (the names correspond to a DEC VT220).  In Linux console, that
"Del" sends the same escape sequence as "Delete".

If you're using some other terminal, then the issue probably isn't Lynx.

If I've overlooked some detail, steps-to-reproduce would be helpful.

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


signature.asc
Description: Digital signature

Bug#891685: castle-game-engine: FTBFS on m68k: color and vector tests fail

[Aaron M. Ucko]

Source: castle-game-engine
Version: 6.4+dfsg1-2
Severity: normal
Tags: upstream
User: debian-...@lists.debian.org
Usertags: m68k

Builds of castle-game-engine for m68k (admittedly not a release
architecture) have been failing.  In addition to the general
big-endian test suite issues I reported as #891684, there are four
more I see only on m68k [1]:

  Failure: 
Message:   TTestCastleColors.TestHSV: 
Exception class:   EAssertionFailedError
Exception message: 
at   $8007A68A  TTESTCASTLECOLORS__TESTHSV,  line 62 of 
tests/testcastlecolors.pas
  Failure: 
Message:   TTestImagesDraw.TestDrawToRgb: Vectors (TVector3Byte) 
are not equal: expected: 2 3 32, actual: 2 3 11
Exception class:   EAssertionFailedError
Exception message: Vectors (TVector3Byte) are not equal: expected: 2 3 32, 
actual: 2 3 11
at   $802E59AC  TCASTLEBASETESTCASE__ASSERTVECTOREQUALS,  line 109 of 
tests/castlebasetestcase.pas
  Failure: 
Message:   TTestImagesDraw.TestDrawToGrayscaleAlpha: Vectors 
(TVector2Byte) are not equal: expected: 111 128, actual: 103 128
Exception class:   EAssertionFailedError
Exception message: Vectors (TVector2Byte) are not equal: expected: 111 128, 
actual: 103 128
at   $802E5842  TCASTLEBASETESTCASE__ASSERTVECTOREQUALS,  line 101 of 
tests/castlebasetestcase.pas
  Failure: 
Message:   TTestCastleSceneManager.TestLoadLevel: Vectors 
(TVector3) are not equal: expected: 2.15621185302734 2 -2.33851003646851, 
actual: 3.2496919631958 2 -5.4161548614502
Exception class:   EAssertionFailedError
Exception message: Vectors (TVector3) are not equal: expected: 
2.15621185302734 2 -2.33851003646851, actual: 3.2496919631958 2 -5.4161548614502
at   $802E615E  TCASTLEBASETESTCASE__ASSERTVECTOREQUALS,  line 151 of 
tests/castlebasetestcase.pas

Could you please take a look?

Thanks!

[1] 
https://buildd.debian.org/status/fetch.php?pkg=castle-game-engine=m68k=6.4%2Bdfsg1-2=1518961263=0

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#858962: enabling OVMF - 4.10+

[Hans van Kranenburg]

On 28/02/2018 00:59, John Keates wrote:
> Here is how you can test it:
> 
> [...]

Thanks! This is really helpful. I'm going to try this tomorrow.

Hans

Bug#888062:

[Andreas Beckmann]

I uploaded 1.1~rc2 to experimental yesterday and we got a successful
arm64 build that passed all the tests.

Thanks!

Andreas

Bug#891684: castle-game-engine: FTBFS (big-endian): lookup and hashing tests fail

[Aaron M. Ucko]

Source: castle-game-engine
Version: 6.4+dfsg1-2
Severity: important
Tags: upstream
Justification: fails to build from source
User: debian-powe...@lists.debian.org
Usertags: powerpc ppc64

Builds of castle-game-engine for big-endian architectures that get as
far as running the test suite (so not mips at present, per #891683)
have been failing with errors along the lines of

  Number of run tests: 227
  Number of errors:2
  Number of failures:  1
  
  List of errors:
Error: 
  Message:   TTestX3DNodes.TestRootNodeMeta: Dictionary key does 
not exist
  Exception class:   EListError
  Exception message: Dictionary key does not exist
  at   $103FE5D0 line 372 of ./src/base/castlegenericlists.pas
  
Error: 
  Message:   TTestGame.TestGameData: Resource type "WalkAttack" not 
found, mentioned in file 
"file:///«BUILDDIR»/castle-game-engine-6.4+dfsg1/tests/data/game/resource.xml"
  Exception class:   Exception
  Exception message: Resource type "WalkAttack" not found, mentioned in 
file 
"file:///«BUILDDIR»/castle-game-engine-6.4+dfsg1/tests/data/game/resource.xml"
  at   $10773D20 line 372 of ./src/base/castlegenericlists.pas
  
  
  List of failures:
Failure: 
  Message:   TTestCastleRandom.TestHash:  expected: <3762729884> 
but was: <3168055629>
  Exception class:   EAssertionFailedError
  Exception message:  expected: <3762729884> but was: <3168055629>
  at   $100BFA34  TTESTCASTLERANDOM__TESTHASH,  line 42 of 
tests/testcastlerandom.pas

There are four additional failures on m68k; I'll report them
separately.

Could you please take a look?

Thanks!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#891683: castle-game-engine: FTBFS on mips(el): Cannot load FreeType library

[Aaron M. Ucko]

Source: castle-game-engine
Version: 6.4+dfsg1-2
Severity: important
Tags: upstream
Justification: fails to build from source
User: debian-m...@lists.debian.org
Usertags: mips mipsel

Builds of castle-game-engine for mips [1] and mipsel [2] have been
failing with errors along the lines of

  Linking 
/<>/castle-game-engine-6.4+dfsg1/debian/tmp/tmp/texture-font-to-pascal
  /usr/bin/ld.bfd: warning: 
/<>/castle-game-engine-6.4+dfsg1/debian/tmp/tmp/link.res contains 
output sections; did you forget -T?
  /usr/bin/ld.bfd: 
/usr/lib/mips-linux-gnu/fpc/3.0.4/units/mips-linux/rtl/system.o: warning: 
linking abicalls files with non-abicalls files
  [...]
  /usr/bin/ld.bfd: 
/<>/castle-game-engine-6.4+dfsg1/debian/tmp/tmp/castleinternalftfont.o:
 warning: linking abicalls files with non-abicalls files
  76110 lines compiled, 42.9 sec
  cd src/fonts ; 
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/<>/castle-game-engine-6.4+dfsg1/debian/tmp/tmp
 ./mk_fonts.sh
  + TEXTUREFONT2PASCAL=texture-font-to-pascal
  + TEXT_NODE_FONT_SIZE=20
  + texture-font-to-pascal --size 20 
/usr/share/fonts/truetype/dejavu/DejaVuSans-BoldOblique.ttf --unit-name 
CastleTextureFont_DjvSansBO_20
  An unhandled exception occurred at $00609C6C:
  EFreeTypeLibraryNotFound: Cannot load FreeType library, loading font files 
not possible
$00609C6C
$0074B36C
$00537AC8
$0045855C
$00457DB4

Could you please take a look?

Thanks!

[1] 
https://buildd.debian.org/status/fetch.php?pkg=castle-game-engine=mips=6.4%2Bdfsg1-2=1518388715=0
[2] 
https://buildd.debian.org/status/fetch.php?pkg=castle-game-engine=mipsel=6.4%2Bdfsg1-2=1518390291=0

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#858962: [Pkg-xen-devel] Bug#858962: enabling OVMF - 4.10+

[John Keates]

HI Hans,

We probably should update the mailing list anyway since not everybody will be 
on GitLab anyway. Here is how you can test it:

1. Install Xen with OVMF support
2. Install OVMF (which basically just gets you the binary file, package is 
called ovmf)
3. Get an EFI-bootable image, the Debian Netinstall image will probably do fine
3. Create a domU config like this:

name = 'uefi-domu-thingy'
bios = "ovmf"
builder = 'hvm'
memory = '512'
vcpus = 1

Then sudo xl create 

This should start the domu, and since there is no disk, just get to the UEFI 
shell and idle around and not do much else. You can connect to it over VNC, but 
I’m sure it can be started in UEFI text mode too so you get UEFI access via the 
serial console.

If you want to test booting an OS, a simple way is starting debian. Grabbing 
the netinstall image works, add a disk stanza and there you go:

disk = ['file:/tmp/debian-9.3.0-amd64-netinst.iso,xvda’]

If you want to control the virtual frame buffer VNC setup:

vfb = ["type=vnc, vnclisten=0.0.0.0, vncpasswd=1337-haxx0r"]

If you also want to have some networking fun, you could add a virtual interface 
as normal:

vif = [ 'mac=00:16:3e:12:34:56, bridge=testlan0, script=vif-openvswitch, 
type=vif’]

By the way, if OVMF isn’t enabled or the ovmf.fd file doesn’t exist in the 
expected or configured path, it will error out.

- John

> On 28 Feb 2018, at 00:18, Hans van Kranenburg  wrote:
> 
> Hi John,
> 
> I don't think this will ever hit 4.8 in stable, but I want to have this
> in the new 4.10+ packages for unstable because you've been waiting long
> enough now.
> 
> Thanks for sending the Merge Request about this. Now the change will go
> in under your name. :)
> 
> I don't think that a discussion in gitlab on some commit that got
> rebased later is the best way, so let's continue here.
> 
> I know --enable-ovmf builds ok, now I need instructions to test this. I
> suspect you're on 4.8 and unless you have a spare test system already
> you might not want to be running random experimental test builds for
> 4.10. It also needs rebuilt qemu packages against xen 4.10.
> 
> So, what is the minimal set of things I can do to make sure the
> resulting build does something sensible? I have to be honest I'm not a
> qemu user myself, so I might not be totally familiar with all steps.
> 
> I see https://wiki.xenproject.org/wiki/OVMF which has an example, which
> also mentions use of a live CD.
> 
> Can you point me so something I can provide as a disk, and tell me if
> this is the right path to a minimal test to check that everything is
> working right?
> 
> Thanks,
> Hans
> 
> ___
> Pkg-xen-devel mailing list
> pkg-xen-de...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-xen-devel

Bug#891682: castle-game-engine: FTBFS on arm64: assorted test suite errors and failures

[Aaron M. Ucko]

Source: castle-game-engine
Version: 6.4+dfsg1-2
Severity: important
Tags: upstream
Justification: fails to build from source
User: debian-...@lists.debian.org
Usertags: arm64

Builds of castle-game-engine for arm64 have been failing.  As of the
latest upload (6.4+dfsg1-2), it ran into an assortment of test suite
errors and failures, per the below excerpts from [1].  Could you
please take a look?

Thanks!

[1] 
https://buildd.debian.org/status/fetch.php?pkg=castle-game-engine=arm64=6.4%2Bdfsg1-2=1518389184=0

--

Number of run tests: 227
Number of errors:9
Number of failures:  2

List of errors:
  Error: 
Message:   TTestCastleScript.Test1: Math error EInvalidOp: Invalid 
floating point operation
Exception class:   ECasScriptAnyMathError
Exception message: Math error EInvalidOp: Invalid floating point operation
at   $009951D0

  Error: 
Message:   TTestCastleScript.TestCodeCreatedExprs: Math error 
EInvalidOp: Invalid floating point operation
Exception class:   ECasScriptAnyMathError
Exception message: Math error EInvalidOp: Invalid floating point operation
at   $009951D0

  Error: 
Message:   TTestCastleScript.TestFloatPrograms: Math error 
EInvalidOp: Invalid floating point operation
Exception class:   ECasScriptAnyMathError
Exception message: Math error EInvalidOp: Invalid floating point operation
at   $009951D0

  Error: 
Message:   TTestCastleScript.TestVariousTypesPrograms: Math error 
EInvalidOp: Invalid floating point operation
Exception class:   ECasScriptAnyMathError
Exception message: Math error EInvalidOp: Invalid floating point operation
at   $009951D0

  Error: 
Message:   TTestCastleScript.TestArrays: Math error EInvalidOp: 
Invalid floating point operation
Exception class:   ECasScriptAnyMathError
Exception message: Math error EInvalidOp: Invalid floating point operation
at   $009951D0

  Error: 
Message:   TTestCastleScript.TestBools: Math error EInvalidOp: 
Invalid floating point operation
Exception class:   ECasScriptAnyMathError
Exception message: Math error EInvalidOp: Invalid floating point operation
at   $009951D0

  Error: 
Message:   TTestCastleScriptVectors.TestVecSingle: Integer error 
EDivByZero: Division by zero
Exception class:   ECasScriptAnyMathError
Exception message: Integer error EDivByZero: Division by zero
at   $009950E8

  Error: 
Message:   TTestCastleScriptVectors.TestVecDouble: Integer error 
EDivByZero: Division by zero
Exception class:   ECasScriptAnyMathError
Exception message: Integer error EDivByZero: Division by zero
at   $009950E8

  Error: 
Message:   TTestCastleScriptVectors.TestMatrixSingle: Integer error 
EDivByZero: Division by zero
Exception class:   ECasScriptAnyMathError
Exception message: Integer error EDivByZero: Division by zero
at   $009950E8


List of failures:
  Failure: 
Message:   TTestRectangles.TestScaleEmpty:  expected: <0> but was: 
<429496729600>
Exception class:   EAssertionFailedError
Exception message:  expected: <0> but was: <429496729600>
at   $004C57C4
  Failure: 
Message:   TTestSceneCore.TestBorderManifoldEdges:  expected: <0> 
but was: <14>
Exception class:   EAssertionFailedError
Exception message:  expected: <0> but was: <14>
at   $004C57C4



y do anything
WARNING: OpenAL cannot be initialized, TestLoadBufferException doesn't really 
do anything
s not a TAbstractChildNode, ignoring event
Heap dump by heaptrc unit
1275583 memory blocks allocated : 435181610/440113224
1273829 memory blocks freed : 435078613/440010168
1754 unfreed memory blocks : 102997
True heap size : 2260992
True free heap : 1884800
Should be : 1933424
Call trace for block $7FEA11C0 size 96
  $00413664
  $0099ADA4
  $00999CB8
  $00995094
  $0099B6E8
  $004B8A34 line 260 of tests/testcastlescriptvectors.pas
  $004C57C4
  $004C5654
[...]
Call trace for block $7F8E0700 size 56
  $00414508
  $009A059C
  $0099B430
  $009FEA98
  $009FF680
  $004B3F28 line 125 of tests/testcastlescript.pas
  $004C57C4
  $004C5654
Call trace for block $7F85DB00 size 24
  $debian/rules:114: recipe for target 'override_dh_auto_test-arch' failed
make[1]: *** [override_dh_auto_test-arch] Error 1

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#891465: glpk: prints warnings which lead to failing sagemath tests

[Mike Miller]

Package: libglpk40
Version: 4.65-1
Followup-For: Bug #891465

Hi, I also see this bug affecting octave, although as a minor cosmetic
issue. Octave's glpk unit tests also intentionally set msg_lev to
GLP_MSG_OFF to have no output generated. With glpk 4.65, this same
message is now appearing in the test suite output log.

It would be very helpful if GLP_MSG_OFF suppressed this message as it
does with other messages.

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

Kernel: Linux 4.14.0-3-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 /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libglpk40 depends on:
ii  libamd2 1:5.1.2-2
ii  libc6   2.26-6
ii  libcolamd2  1:5.1.2-2
ii  libgmp102:6.1.2+dfsg-2
ii  libltdl72.4.6-2
ii  zlib1g  1:1.2.8.dfsg-5

libglpk40 recommends no packages.

Versions of packages libglpk40 suggests:
pn  default-libmysqlclient-dev  
pn  libiodbc2-dev   

-- no debconf information

Bug#891681: python3-nova: fails to upgrade from 'testing' - trying to overwrite /usr/share/apport/package-hooks/source_nova.py

[Andreas Beckmann]

Package: python3-nova
Version: 2:17.0.0~rc1-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Selecting previously unselected package python3-nova.
  Preparing to unpack .../189-python3-nova_2%3a17.0.0~rc1-2_all.deb ...
  Unpacking python3-nova (2:17.0.0~rc1-2) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-qyNCaS/189-python3-nova_2%3a17.0.0~rc1-2_all.deb 
(--unpack):
   trying to overwrite '/usr/share/apport/package-hooks/source_nova.py', which 
is also in package python-nova 2:16.0.3-10
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-qyNCaS/189-python3-nova_2%3a17.0.0~rc1-2_all.deb


cheers,

Andreas


python-nova=2%16.0.3-10_python3-nova=2%17.0.0~rc1-2.log.gz
Description: application/gzip

Bug#858962: enabling OVMF - 4.10+

[Hans van Kranenburg]

Hi John,

I don't think this will ever hit 4.8 in stable, but I want to have this
in the new 4.10+ packages for unstable because you've been waiting long
enough now.

Thanks for sending the Merge Request about this. Now the change will go
in under your name. :)

I don't think that a discussion in gitlab on some commit that got
rebased later is the best way, so let's continue here.

I know --enable-ovmf builds ok, now I need instructions to test this. I
suspect you're on 4.8 and unless you have a spare test system already
you might not want to be running random experimental test builds for
4.10. It also needs rebuilt qemu packages against xen 4.10.

So, what is the minimal set of things I can do to make sure the
resulting build does something sensible? I have to be honest I'm not a
qemu user myself, so I might not be totally familiar with all steps.

I see https://wiki.xenproject.org/wiki/OVMF which has an example, which
also mentions use of a live CD.

Can you point me so something I can provide as a disk, and tell me if
this is the right path to a minimal test to check that everything is
working right?

Thanks,
Hans

Bug#891680: Cannot bind to "any" address family

[martin f krafft]

Package: taskd
Version: 1.1.0+dfsg-3
Severity: normal
Tags: ipv6 upstream
Forwarded: https://github.com/GothenburgBitFactory/taskwarrior/issues/1972

taskd honours the `family` setting in its config file, even defaults
to "any". However, only one `server` setting will ever be read, so
unless sys.net.ipv6.ip_nonlocal_bind is on, there is no way to make
it listen on IPv4 and IPv6.

It'd be best to let the config specify any number of `server` lines,
and then to bind them all.

Thanks,

-- 
 .''`.   martin f. krafft  @martinkrafft
: :'  :  proud Debian developer
`. `'`   http://people.debian.org/~madduck
  `-  Debian - when you have better things to do than fixing systems


digital_signature_gpg.asc
Description: Digital GPG signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)

Bug#891570: [Pkg-openssl-devel] Bug#891570: [Bug#891570: SSL connect attempt failed error:141A90B5:SSL routines:ssl_cipher_list_to_bytes:no ciphers available

[Kurt Roeckx]

On Tue, Feb 27, 2018 at 09:39:11PM +0100, Sebastian Andrzej Siewior wrote:
> control: clone -1 -2
> control: reassign -2 libio-socket-ssl-perl 2.056-1
> control: severity -2 normal
> control: tags -2 patch
> 
> On 2018-02-27 21:52:23 [+0800], 積丹尼 Dan Jacobson wrote:
> > Here is all you need to reproduce it:
> > 
> > $ mech-dump https://mbasic.facebook.com/
> > POST 
> > https://mbasic.facebook.com/login.php?refsrc=https%3A%2F%2Fmbasic.facebook.com%2F=100=8
> > 
> > Now  upgrade libssl1.1:amd64 1.1.0g-2 1.1.1~~pre1-1
> > 
> > $ mech-dump https://mbasic.facebook.com/
> > Error GETing https://mbasic.facebook.com/: Can't connect to 
> > mbasic.facebook.com:443 (SSL connect attempt failed error:141A90B5:SSL 
> > routines:ssl_cipher_list_to_bytes:no ciphers available) at 
> > /usr/bin/mech-dump line 68.
> > $ dlocate mech-dump
> > libwww-mechanize-perl: /usr/bin/mech-dump
> 
> Thank you. This was helpfull.
> The problem is that libio-socket-ssl-perl has a predefined cipher list
> which does not include any TLS1.3 cipher (yes, it has its own). The
> patch attached adds TLS1.3 cipher which means that it is possible to
> negotiate a TLS1.3 connection if the remote side supports it.
> 
> I cloned the bug and hope that openssl falls back to TLS1.2 only
> connection if the ciphers are missing especially if the remote side does
> not support 1.3. Lets see about that…

I wasn't exactly expecting this problem, I would have expected a
different error message as mentioned in the blog:
139998555496896:error:141A90B5:SSL routines:ssl_cipher_list_to_bytes:no ciphers 
available:ssl/statem/statem_clnt.c:3720:No ciphers enabled for max supported 
SSL/TLS version

But note that we're actually changing that behaviour in
https://github.com/openssl/openssl/pull/5392

That said, in general I think it's a bad idea for applications and
libraries to override the defaults. OpenSSL has sane defaults, and
if you want to exclude some ciphers I suggest you start from
DEFAULT and remove some and not create your own list of which one
you want to support.

> + 'TLS13-CHACHA20-POLY1305-SHA256',
> + 'TLS13-AES-256-GCM-SHA384',
> + 'TLS13-AES-128-GCM-SHA256',
> + 'TLS13-AES-128-CCM-8-SHA256',
> + 'TLS13-AES-128-CCM-SHA256',

You probably don't want the CCM ones by default.


Kurt

Bug#891374: [Pkg-mailman-hackers] Bug#891374: python-django-postorius: broken symlinks: /usr/share/doc/python-django-postorius/html/_static/*

[Pierre-Elliott Bécue]

Le dimanche 25 février 2018 à 01:09:01+0100, Andreas Beckmann a écrit :
> Package: python-django-postorius
> Version: 1.1.2-1
> Severity: normal
> User: debian...@lists.debian.org
> Usertags: piuparts
> 
> Hi,
> 
> during a test with piuparts I noticed your package ships (or creates)
> a broken symlink.
> 
> From the attached log (scroll to the bottom...):
> 
> 1m4.0s ERROR: FAIL: Broken symlinks:
>   /usr/share/doc/python-django-postorius/html/_static/js/theme.js -> 
> ../../../../../sphinx_rtd_theme/static/js/theme.js
>   /usr/share/doc/python-django-postorius/html/_static/js/modernizr.min.js -> 
> ../../../../../sphinx_rtd_theme/static/js/modernizr.min.js
>   
> /usr/share/doc/python-django-postorius/html/_static/fonts/fontawesome-webfont.woff
>  -> ../../../../../sphinx_rtd_theme/static/fonts/fontawesome-webfont.woff
>   
> /usr/share/doc/python-django-postorius/html/_static/fonts/fontawesome-webfont.ttf
>  -> ../../../../../sphinx_rtd_theme/static/fonts/fontawesome-webfont.ttf
>   
> /usr/share/doc/python-django-postorius/html/_static/fonts/fontawesome-webfont.svg
>  -> ../../../../../sphinx_rtd_theme/static/fonts/fontawesome-webfont.svg
>   
> /usr/share/doc/python-django-postorius/html/_static/fonts/fontawesome-webfont.eot
>  -> ../../../../../sphinx_rtd_theme/static/fonts/fontawesome-webfont.eot
>   
> /usr/share/doc/python-django-postorius/html/_static/fonts/RobotoSlab-Regular.ttf
>  -> ../../../../../sphinx_rtd_theme/static/fonts/RobotoSlab-Regular.ttf
>   
> /usr/share/doc/python-django-postorius/html/_static/fonts/RobotoSlab-Bold.ttf 
> -> ../../../../../sphinx_rtd_theme/static/fonts/RobotoSlab-Bold.ttf
>   /usr/share/doc/python-django-postorius/html/_static/fonts/Lato-Regular.ttf 
> -> ../../../../../sphinx_rtd_theme/static/fonts/Lato-Regular.ttf
>   /usr/share/doc/python-django-postorius/html/_static/fonts/Lato-Bold.ttf -> 
> ../../../../../sphinx_rtd_theme/static/fonts/Lato-Bold.ttf
>   
> /usr/share/doc/python-django-postorius/html/_static/fonts/Inconsolata-Regular.ttf
>  -> ../../../../../sphinx_rtd_theme/static/fonts/Inconsolata-Regular.ttf
>   
> /usr/share/doc/python-django-postorius/html/_static/fonts/Inconsolata-Bold.ttf
>  -> ../../../../../sphinx_rtd_theme/static/fonts/Inconsolata-Bold.ttf
>   /usr/share/doc/python-django-postorius/html/_static/css/theme.css -> 
> ../../../../../sphinx_rtd_theme/static/css/theme.css
>   /usr/share/doc/python-django-postorius/html/_static/css/badge_only.css -> 
> ../../../../../sphinx_rtd_theme/static/css/badge_only.css
> 
> Is python-django-postorius missing a
> Depends/Recommends/Suggests: sphinx-rtd-theme-common?

Dear Andreas,

That makes perfect sense, thanks for the hint!

I'll have a look at it soon.

Cheers!

-- 
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528  F493 0D44 2664 1949 74E2
It's far easier to fight for one's principles than to live up to them.


signature.asc
Description: PGP signature

Bug#889859: chemps2: FTBFS on mipsel: test5 segfaults

[Aurelien Jarno]

On 2018-02-09 09:21, Sebastian Wouters wrote:
> Dear Aaron,
> 
> To be honest, I haven't got the fogiest.
> 
> On other architectures, it works fine. And test5 hasn't been individually
> changed since v1.8 was released (24 Aug 2016):
> 
> https://github.com/SebWouters/CheMPS2/commits/master/tests/test5.cpp.in
> https://github.com/SebWouters/CheMPS2/releases
> 
> Could it be that it was an individual accidental seg fault, which doesn't
> re-occur upon running another time?

It seems to be an issue with the Loongson 3 buildds, it built fine on
other buildds. I have blacklisted it on the Loongson 3 buildds so that
it doesn't happen again.

I am therefore closing the bug.

Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net

Bug#891679: libc++: FTBFS with glibc 2.27: Failing Tests

[Aurelien Jarno]

Source: libc++
Version: 5.0.1-1
Severity: important
Tags: patch
User: debian-gl...@lists.debian.org
Usertags: 2.27

libc++ 5.0.1-1 fails to build with glibc 2.27 (2.27-0experimental0 from
experimental):

| 
| Failing Tests (5):
| libc++ :: 
std/localization/locale.categories/category.monetary/locale.money.get/locale.money.get.members/get_long_double_fr_FR.pass.cpp
| libc++ :: 
std/localization/locale.categories/category.monetary/locale.money.put/locale.money.put.members/put_long_double_fr_FR.pass.cpp
| libc++ :: 
std/localization/locale.categories/category.monetary/locale.moneypunct.byname/decimal_point.pass.cpp
| libc++ :: 
std/localization/locale.categories/category.monetary/locale.moneypunct.byname/thousands_sep.pass.cpp
| libc++ :: 
std/localization/locale.categories/facet.numpunct/locale.numpunct.byname/thousands_sep.pass.cpp

A full build log is available there:
http://aws-logs.debian.net/2018/02/07/glibc-exp/libc++_5.0.1-1_unstable_glibc-exp.log

This failing tests are due to changes in the locales introduced in glibc
2.27, which causes the expected value to change. And more precisely the
following two changes:

| commit f11f2f6e145d6fc6b52f6b0733599f8b96595733
| Author: Mike FABIAN 
| Date:   Tue Aug 29 13:39:18 2017 +0200
| 
| Use “,” as mon_decimal_point for ru_RU and os_RU locales (follow CLDR)
| 
| [BZ #13805]
| * locales/ru_RU (LC_MONETARY): Use “,” for mon_decimal_point
| (to agree with CLDR).
| * locales/ru_RU (LC_NUMERIC): Write mon_decimal_point in ASCII
| for readability.
| * locales/os_RU (LC_MONETARY): Copy from ru_RU,
| makes it agree with CLDR.

and

| commit 70a6707fa15e63591d991761be025e26e8d02bb6
| Author: Stanislav Brabec 
| Date:   Wed Nov 2 16:52:58 2016 +0100
| 
| Locales: Use Unicode wise thousands separator
| 
| Many languages use small gap as thousands separator.
| 
| Thousands separator should not be a plain space, but a narrow space.
| And additionally, it is not allowed to wrap line in the middle of the
| number.
| 
| Locale data were created in a deep age of 8-bit encodings, so most of
| them use space (incorrect: it allows wrapping the line in the middle
| of the number), or NBSP (better, but typographically incorrect: space
| between groups is too wide).
| 
| Now UNICODE is widely supported, so we should leave legacy characters
| in favor of correct UNICODE character.
| 
| UNICODE has a dedicated character for this purpose:
| 
| NNBSP
| U+202F NARROW NO-BREAK SPACE: a narrow form of a no-break space,
| typically the width of a thin space or a mid space
| 
| The NNBSP exists since Unicode 3.0.
| 
| Use of NNBSP will prevent line wrapping in the midle of number and
| improve readability of numbers.

I have attached a patch to do the corresponding changes on the libc++
side. Note however they are not conditional, meaning that they won't
work with glibc 2.26 or older. I guess the correct way to do that
depends on upstream.
--- 
libc++-5.0.1.orig/libcxx/test/std/localization/locale.categories/category.monetary/locale.money.get/locale.money.get.members/get_long_double_fr_FR.pass.cpp
+++ 
libc++-5.0.1/libcxx/test/std/localization/locale.categories/category.monetary/locale.money.get/locale.money.get.members/get_long_double_fr_FR.pass.cpp
@@ -84,7 +84,7 @@ int main()
 assert(ex == -1);
 }
 {   // positive
-std::string v = "1 234 567,89 ";
+std::string v = "1\177234\177567,89 ";
 typedef input_iterator I;
 long double ex;
 std::ios_base::iostate err = std::ios_base::goodbit;
@@ -95,7 +95,7 @@ int main()
 assert(ex == 123456789);
 }
 {   // negative
-std::string v = "-1 234 567,89";
+std::string v = "-1\177234\177567,89";
 typedef input_iterator I;
 long double ex;
 std::ios_base::iostate err = std::ios_base::goodbit;
@@ -164,7 +164,7 @@ int main()
 assert(ex == -1);
 }
 {   // positive, showbase
-std::string v = "1 234 567,89 \u20ac";
+std::string v = "1\177234\177567,89 \u20ac";
 typedef input_iterator I;
 long double ex;
 std::ios_base::iostate err = std::ios_base::goodbit;
@@ -175,7 +175,7 @@ int main()
 assert(ex == 123456789);
 }
 {   // positive, showbase
-std::string v = "1 234 567,89 \u20ac";
+std::string v = "1\177234\177567,89 \u20ac";
 showbase(ios);
 typedef input_iterator I;
 long double ex;
@@ -188,7 +188,7 @@ int main()
 noshowbase(ios);
 }
 {   // negative, showbase
-std::string v = "-1 234 567,89 \u20ac";
+   

Bug#891678: O: libcommoncpp2

[Bernhard Schmidt]

Package: wnpp
Severity: normal

Hi,

on behalf of the Debian VoIP team I'm orphaning src:libcommoncpp2 . It has not
been properly maintained for several years.

There are a few rdeps in the archive outside of the VoIP team

Checking reverse dependencies...
# Broken Depends:
clamfs: clamfs [amd64 arm64 armel armhf i386 kfreebsd-amd64 kfreebsd-i386 mips 
mips64el mipsel powerpc ppc64el s390x]
libccscript3: libccscript3-1.1-0
  libccscript3-dev
ui-utilcpp: libui-utilcpp-dev [amd64 arm64 armel armhf i386 mips mips64el 
mipsel powerpc ppc64el s390x]
libui-utilcpp9v5 [amd64 arm64 armel armhf i386 mips mips64el mipsel 
powerpc ppc64el s390x]

# Broken Build-Depends:
clamfs: libcommoncpp2-dev
libccscript3: libcommoncpp2-dev
ui-utilcpp: libcommoncpp2-dev
vdr-plugin-fritzbox: libcommoncpp2-dev

For libccscript3 a RM bug has been filed.

Bernhard

Bug#891677: postfixadmin: New upstream release: 3.1

[Gabriel Filion]

Package: postfixadmin
Version: 3.0.2-2
Severity: normal

Hello,

A new release of postfix admin happened in june 2017 : 3.1. It would be
nice to package this version in sid/testing

Also, the code was officially (so I was told by cboltz on the
#postfixadmin irc channel on freenode) moved to github now:

https://github.com/postfixadmin/postfixadmin

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

Kernel: Linux 4.9.0-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_CA.utf8), LANGUAGE=en_CA:en (charmap=UTF-8) (ignored: LC_ALL set to 
en_CA.utf8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages postfixadmin depends on:
ic  apache2 [httpd] 2.4.25-3
ii  dbconfig-common 2.0.8
ii  debconf 1.5.61
ii  default-mysql-client1.0.2
ii  nginx-full [httpd]  1.10.3-1+deb9u1
ii  php-fpm 1:7.0+49
ii  php-imap1:7.0+49
ii  php-mbstring1:7.0+49
ii  php-mysql   1:7.0+49
ii  php7.0-fpm [php-fpm]7.0.19-1
ii  php7.0-imap [php-imap]  7.0.19-1
ii  php7.0-mbstring [php-mbstring]  7.0.19-1
ii  php7.0-mysql [php-mysqlnd]  7.0.19-1
ii  wwwconfig-common0.3.0

Versions of packages postfixadmin recommends:
ii  dovecot-core1:2.2.27-3+deb9u1
ii  mariadb-server  10.1.26-0+deb9u1
ii  mariadb-server-10.1 [virtual-mysql-server]  10.1.26-0+deb9u1
ii  php7.0-cli [php-cli]7.0.19-1
ii  postfix-mysql   3.1.6-0+deb9u1
pn  zendframework   

postfixadmin suggests no packages.

-- debconf information:
  postfixadmin/internal/reconfiguring: false
* postfixadmin/db/app-user: postfixadmin@localhost
* postfixadmin/database-type: mysql
* postfixadmin/dbconfig-reinstall: true
  postfixadmin/upgrade-backup: true
  postfixadmin/purge: false
* postfixadmin/reconfigure-webserver:
* postfixadmin/db/dbname: postfixadmin
* postfixadmin/mysql/admin-user: debian-sys-maint
  postfixadmin/dbconfig-remove:
  postfixadmin/upgrade-error: abort
  postfixadmin/pgsql/admin-user: postgres
  postfixadmin/pgsql/manualconf:
  postfixadmin/missing-db-package-error: abort
* postfixadmin/mysql/method: Unix socket
  postfixadmin/internal/skip-preseed: false
  postfixadmin/pgsql/authmethod-user: password
  postfixadmin/pgsql/changeconf: false
  postfixadmin/db/basepath:
  postfixadmin/remote/newhost:
  postfixadmin/pgsql/authmethod-admin: ident
  postfixadmin/pgsql/method: TCP/IP
  postfixadmin/dbconfig-upgrade: true
  postfixadmin/remote/port:
* postfixadmin/dbconfig-install: true
  postfixadmin/remove-error: abort
  postfixadmin/pgsql/no-empty-passwords:
  postfixadmin/remote/host: localhost
  postfixadmin/passwords-do-not-match:
* postfixadmin/install-error: ignore

Bug#891676: RM: libccscript3 -- ROM; outdated, unmaintained, no rdeps

[Bernhard Schmidt]

Package: ftp.debian.org
Severity: normal

Hi,

on behalf of the Debian VoIP team I'm requesting removal of src:libccscript3
from the archive. It does not have any rdeps within Debian and has not been
properly maintained for years.

Best Regards,
Bernhard

Bug#891675: RM: libccaudio2 -- ROM; outdated, unmaintained, no rdeps

[Bernhard Schmidt]

Package: ftp.debian.org
Severity: normal

Hi,

on behalf of the Debian VoIP team I'm requesting the removal of src:libccaudio2
from the archive. It does not have any rdeps within Debian and has not been
properly maintained for years.

Best Regards,
Bernhard

Bug#891674: xserver-xorg-core: crashes if started as root

[Peter.Chubb]

Package: xserver-xorg-core
Version: 2:1.19.6-1
Severity: important

Dear Maintainer,

I can start Xorg using startx as an ordinary user (it uses 
the modesetting driver).
But when the display manager starts it (as root) it crashes.

The only `interesting' thing about this machine I'm aware of (apart
from it being a very recent Skylake architecture machine) is that all
the storage is under a VMD domain.  I've appended the output of lspci,
as the crash occurs when scanning the PCI bus as root.

GDB shows
(gdb) bt
#0  0x77019cc8 in pci_device_next ()
   from /usr/lib/x86_64-linux-gnu/libpciaccess.so.0
#1  0x77019d4b in pci_device_find_by_slot ()
   from /usr/lib/x86_64-linux-gnu/libpciaccess.so.0
#2  0x7701b9ca in pci_device_vgaarb_init ()
   from /usr/lib/x86_64-linux-gnu/libpciaccess.so.0
#3  0x55604d99 in ?? ()
#4  0x555de8e2 in xf86BusConfig ()
#5  0x555ecb68 in InitOutput ()
#6  0x555aab83 in ?? ()
#7  0x75362f2a in __libc_start_main (main=0x55594a00, argc=2, 
argv=0x7fffec38, init=, fini=, 
rtld_fini=, stack_end=0x7fffec28)
at ../csu/libc-start.c:310
#8  0x55594a3a in _start ()




-- Package-specific info:
/etc/X11/X does not exist.
/etc/X11/X is not a symlink.
/etc/X11/X is not executable.

VGA-compatible devices on PCI bus:
--
:65:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF119 [NVS 
315] [10de:107c] (rev a1)

/etc/X11/xorg.conf does not exist.

Contents of /etc/X11/xorg.conf.d:
-
total 0

/etc/modprobe.d contains no KMS configuration files.

Kernel version (/proc/version):
---
Linux version 4.15.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 
7.3.0 (Debian 7.3.0-3)) #1 SMP Debian 4.15.4-1 (2018-02-18)

Xorg X server log files on system:
--
-rw-r--r-- 1 peterc peterc 56283 Feb 28 07:58 
/home/peterc/.local/share/xorg/Xorg.0.log
-rw-r--r-- 1 root   root5054 Feb 28 08:05 /var/log/Xorg.0.log

Contents of most recent Xorg X server log file (/var/log/Xorg.0.log):
-
[ 60011.801] 
X.Org X Server 1.19.6
Release Date: 2017-12-20
[ 60011.801] X Protocol Version 11, Revision 0
[ 60011.801] Build Operating System: Linux 4.9.0-5-amd64 x86_64 Debian
[ 60011.801] Current Operating System: Linux wolf-un 4.15.0-1-amd64 #1 SMP 
Debian 4.15.4-1 (2018-02-18) x86_64
[ 60011.801] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1-amd64 
root=UUID=2cc1510e-8bb0-4e82-b22b-6bb508493d1f ro quiet
[ 60011.801] Build Date: 26 January 2018  04:30:21PM
[ 60011.801] xorg-server 2:1.19.6-1 (https://www.debian.org/support) 
[ 60011.801] Current version of pixman: 0.34.0
[ 60011.801]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 60011.801] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 60011.801] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Feb 28 08:05:36 
2018
[ 60011.801] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 60011.801] (==) No Layout section.  Using the first Screen section.
[ 60011.801] (==) No screen section available. Using defaults.
[ 60011.801] (**) |-->Screen "Default Screen Section" (0)
[ 60011.801] (**) |   |-->Monitor ""
[ 60011.802] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 60011.802] (==) Automatically adding devices
[ 60011.802] (==) Automatically enabling devices
[ 60011.802] (==) Automatically adding GPU devices
[ 60011.802] (==) Max clients allowed: 256, resource mask: 0x1f
[ 60011.802] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[ 60011.802]Entry deleted from font path.
[ 60011.802] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins
[ 60011.802] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 60011.802] (II) The server relies on udev to provide the list of input 
devices.
If no devices become available, reconfigure udev or disable 
AutoAddDevices.
[ 60011.802] (II) Loader magic: 0x55996de0
[ 60011.802] (II) Module ABI versions:
[ 60011.802]X.Org ANSI C Emulation: 0.4
[ 60011.802]X.Org Video Driver: 23.0
[ 60011.802]X.Org XInput driver : 24.1
[ 60011.802]X.Org Server Extension : 10.0
[ 60011.802] (--) using VT number 2

[ 60011.802] (II) systemd-logind: logind integration requires -keeptty and 
-keeptty was not provided, disabling logind integration
[ 60011.803] (II) xfree86: Adding drm device 

Bug#890064: smbios-utils: properly clean up legacy config files

[Mario.Limonciello]

Th warnings come from the dpkg maintscript helper.  You're supposed to put it 
in all the helper scripts and they show warnings for the prerm IIRC.
I guess a separate upgrade task may be needed to delete the directories then 
too if empty.

> -Original Message-
> From: Christoph Anton Mitterer [mailto:cales...@scientia.net]
> Sent: Tuesday, February 27, 2018 2:44 PM
> To: 890...@bugs.debian.org
> Subject: Bug#890064: smbios-utils: properly clean up legacy config files
> 
> Hi.
> 
> Are you sure this has been fixed properly?
> 
> On an upgrade to the new package version I saw:
> Unpacking smbios-utils (2.4.1-1) over (2.3.1-2) ...
> dpkg: warning: unable to delete old directory '/etc/yum/pluginconf.d': 
> Directory
> not empty
> dpkg: warning: unable to delete old directory '/etc/yum': Directory not empty
> 
> and while all these are empty, the dirs are still not removed.
> 
> Cheers,
> Chris.

Bug#891673: collectd: build dependency intel-cmt-cat is only available on amd64+i386

[Adrian Bunk]

Source: collectd
Version: 5.8.0-1
Severity: serious

The new build dependency intel-cmt-cat is only available on amd64+i386,
and should therefore only be used on these architectures.

Bug#736243: network-manager-openvpn-gnome: Can not set certificates properly

[Starchy Grant]

Package: network-manager-openvpn
Version: 1.8.0-2
Followup-For: Bug #736243

Dear Maintainer,

I'm seeing the same behavior in kali-rolling (based on stretch). Whether I 
import the config from an .ovpn file or enter it by hand, every time I save it 
with network-manager-ovpn it appears to save as:

CA certficate: ca.crt
User certificate: ca.crt
User private key: (None)

This is of course unusable. The same config (with the correct user certificate 
and private key) works with openvpn on the command line.

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

Kernel: Linux 4.14.0-kali3-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: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages network-manager-openvpn depends on:
ii  adduser  3.117
ii  libc62.26-6
ii  libglib2.0-0 2.54.3-2
ii  libnm0   1.10.4-1
ii  network-manager  1.10.4-1
ii  openvpn  2.4.4-2

network-manager-openvpn recommends no packages.

network-manager-openvpn suggests no packages.

-- no debconf information

Bug#891670: pymssql FTBFS with freetds-dev 1.00.82-2

[Adrian Bunk]

Source: pymssql
Version: 2.1.3+dfsg-1
Severity: serious

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

...
_mssql.c: In function '__pyx_f_6_mssql__tds_ver_str_to_constant':
_mssql.c:21102:15: error: 'DBVERSION_80' undeclared (first use in this 
function); did you mean 'DBVERSION_70'?
 __pyx_r = DBVERSION_80;
   ^~~~


https://sources.debian.org/src/freetds/1.00.82-2/NEWS/#L6

Bug#891672: libdbi-drivers FTBFS with freetds-dev 1.00.82-2

[Adrian Bunk]

Source: libdbi-drivers
Version: 0.9.0-5
Severity: serious
Tags: buster sid

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

...
dbd_freetds.c: In function 'dbd_connect':
dbd_freetds.c:236:12: error: 'CS_TDS_80' undeclared (first use in this 
function); did you mean 'CS_TDS_70'?
  num = CS_TDS_80;
^


https://sources.debian.org/src/freetds/1.00.82-2/NEWS/#L6

Bug#891671: sqsh FTBFS with freetds-dev 1.00.82-2

[Adrian Bunk]

Source: sqsh
Version: 2.1.7-4
Severity: serious
Tags: buster sid

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

...
cmd_connect.c: In function 'cmd_connect':
cmd_connect.c:809:23: error: 'CS_TDS_80' undeclared (first use in this 
function); did you mean 'CS_TDS_70'?
 version = CS_TDS_80;
   ^
   CS_TDS_70


https://sources.debian.org/src/freetds/1.00.82-2/NEWS/#L6

Bug#891668: stretch-pu: package piglit/0~git20150829-59d7066-1+deb9u1

[Adrian Bunk]

Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian@packages.debian.org
Usertags: pu

   * Add the missing dependency on python-mako. (Closes: #830145)
diff -Nru piglit-0~git20150829-59d7066/debian/changelog 
piglit-0~git20150829-59d7066/debian/changelog
--- piglit-0~git20150829-59d7066/debian/changelog   2015-11-09 
09:44:36.0 +0200
+++ piglit-0~git20150829-59d7066/debian/changelog   2018-02-27 
22:25:56.0 +0200
@@ -1,3 +1,10 @@
+piglit (0~git20150829-59d7066-1+deb9u1) stretch; urgency=medium
+
+  * Non-maintainer upload.
+  * Add the missing dependency on python-mako. (Closes: #830145)
+
+ -- Adrian Bunk   Tue, 27 Feb 2018 22:25:56 +0200
+
 piglit (0~git20150829-59d7066-1) unstable; urgency=low
 
   * Update piglit version
diff -Nru piglit-0~git20150829-59d7066/debian/control 
piglit-0~git20150829-59d7066/debian/control
--- piglit-0~git20150829-59d7066/debian/control 2015-11-09 09:44:36.0 
+0200
+++ piglit-0~git20150829-59d7066/debian/control 2018-02-27 22:25:56.0 
+0200
@@ -26,6 +26,6 @@
 Package: piglit
 Architecture: any
 Depends: ${shlibs:Depends}, ${misc:Pre-Depends}, ${misc:Depends},
- ${python:Depends}, python-six
+ ${python:Depends}, python-six, python-mako
 Description: Open-source test suite for OpenGL implementations
  Piglit is an open-source test suite for OpenGL implementations.

Bug#891669: ITP: nftlb -- nftables load balancer

[Arturo Borrero Gonzalez]

Package: wnpp
Severity: wishlist
Owner: Arturo Borrero Gonzalez 

* Package name: nftlb
  Version : 0.1
  Upstream Author : Laura Garcia 
* URL : https://github.com/zevenet/nftlb
* License : AGPL-3
  Programming Lang: C
  Description : nftables load balancer

nftlb stands for nftables load balancer, the next generation linux firewall that
replaces iptables, is adapted to behave as a complete load balancer and traffic 
distributor.

nftlb is provided with a JSON API, so you can use your preferred health
checker to enable/disable backends or virtual services and automate processed 
with it.

The nftables framework used for load balancing can outperform [0] typical LVS
deployments by 10x.

More info at: https://www.zevenet.com/knowledge-base/nftlb/what-is-nftlb/


[0] https://www.zevenet.com/blog/nftables-load-balancing-10x-faster-lvs/

Bug#872642: stretch-pu: package hdf5/1.10.0-patch1+docs-3

[Gilles Filippini]

Adam D. Barratt a écrit le 27/02/2018 à 20:57 :
> On Tue, 2018-02-27 at 20:53 +0100, Gilles Filippini wrote:
>> Hi,
>>
>> On Sun, 27 Aug 2017 14:03:38 +0100 "Adam D. Barratt"
>>  wrote:
>>> Control: tags -1 + confirmed
>>>
>>> On Sat, 2017-08-19 at 19:20 +0200, Gilles Filippini wrote:
 HDF5 in stretch is affected by RC bug #871506 now fixed in
 unstable and
 testing.
 I have prepared release 1.10.0-patch1+docs-3+deb9u1 for stretch
 with the
 very same fix as in unstable. Debdiff attached.
>>>
>>> Please go ahead.
>>
>> I've just got reminded this pending upload request I had completely
>> forgotten about, because I missed the 'go' which occurred during my
>> holidays.
>> Since it is 6 months old now, could you please confirm that the 'go'
>> is
>> still granted?
> 
> Sure.

Done.

Thanks,

_g.



signature.asc
Description: OpenPGP digital signature

Bug#891662: libcrypto++1: contains libcryptopp.so.6

[GCS]

Control: tags -1 +pending

Hi Andreas,

On Tue, Feb 27, 2018 at 8:46 PM, Andreas Beckmann  wrote:
> during a test with piuparts I noticed your package fails to upgrade from
> 'sid' to 'experimental'.
> It installed fine in 'sid', then the upgrade to 'experimental' fails
> because it tries to overwrite other packages files without declaring a
> Breaks+Replaces relation.
 Thanks for catching this, it's my fault.

> See policy 7.6 at
> https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces
 Indeed, I know the policy.

> Is the SOVERSION 6 => 1 change really a wise idea?
> What happens after the next 5 SOVERSION bumps?
 That would take years as the last SONAME bump was two years ago as
upstream tries to be API / ABI compatible between releases. But the
next upstream SONAME expected to be 7 anyway.

Regards,
Laszlo/GCS

Bug#890547: util-linux: partx fails to read a partition table which fdisk can read

[Patrick Häcker]

Hi,

> See
> https://github.com/yontalcar/util-linux/commit/
> e9ca294aeeec9b32a979024a5f9c23e73325f2b0 
> for patch.

thanks for the fix.
I can confirm, that it works and is more elegant than the version I came up 
with (appended only for the record).

So from my point of view this bug can be closed as soon as the new version 
hits the Debian archive.

Kind regards
Patrick--- util-linux-2.31.1.orig/libblkid/src/partitions/dos.c
+++ util-linux-2.31.1/libblkid/src/partitions/dos.c
@@ -311,8 +311,13 @@ static int probe_dos_pt(blkid_probe pr,
size_t n;
int rc;

-   if (!dos_partition_get_size(p) || is_extended(p))
+   if (!dos_partition_get_size(p) || is_extended(p)) {
+   /* Neutralize increment of i for empty partitions, as p
+* contains all partitions, whereas ls contains only the
+* non-empty ones. */
+   i--;
continue;
+   }

for (n = 0; n < ARRAY_SIZE(dos_nested); n++) {
if (dos_nested[n].type != p->sys_ind)


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

Bug#886068: gtk-theme-config: raising severity of gconf dependency bug

[Jeremy Bicha]

On Tue, Feb 27, 2018 at 4:05 PM, Simon Steinbeiss
 wrote:
> So we will likely drop it from Xubuntu 18.04 and it will become deprecated.
> I guess Debian should drop it too, can't imagine anyone still uses it for
> anything (only the Gtk2 parts still work ok).

I'd be happy to file a Debian removal bug for gtk-theme-config if
that's what y'all want.

(I'm not subscribed to the list so you'll probably need to moderate me through.)

Thanks,
Jeremy Bicha

Bug#891667: bash-completion: file wildcard (*) completion picks up only first match

[Christoph Anton Mitterer]

Package: bash-completion
Version: 1:2.7-1
Severity: normal


Hi.

When completing e.g.
$ ls *

then * doesn't become all the files (not starting with a .), but instead
only one of the files in the directory.

This bug exists now since quite a while, and other bug reports, seem to
include the reason (missing quotes in one of the bash-completion files):
https://bugs.launchpad.net/ubuntu/+source/bash-completion/+bug/1387057
https://superuser.com/questions/823257/unexpected-bash-glob-completion-uses-first-match-even-if-ambiguous

Could this be fixed in the Debian package? :-)

Thanks,
Chris.

Bug#881753: stretch update for local-apt-repository

[Joachim Breitner]

Hi,

Am Dienstag, den 27.02.2018, 21:59 +0200 schrieb Adrian Bunk:
> It is still present in stretch, could you also fix it there?
> Alternatively, I can fix it for stretch if you don't object.

please go ahead, and thanks a lot!

Joachim
-- 
Joachim “nomeata” Breitner
Debian Developer
  nome...@debian.org • https://people.debian.org/~nomeata
  XMPP: nome...@joachim-breitner.de • GPG-Key: 0xF0FBF51F
  https://www.joachim-breitner.de/

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

Bug#886068: gtk-theme-config: raising severity of gconf dependency bug

[Simon Steinbeiss]

Hi Jeremy,

I've worked a little on gtk-theme-config after seeing the Debian bug for
the first time (plus it's actually utterly broken with modern Gtk+3
versions) and to be honest I don't see how it could work with the way
themes are set up these days with sass and resource files. (E.g. changing
the selected-bg-color, which was one of the most prominent features, is
practically impossible to "get right"/consistent results with multiple
themes.)

So we will likely drop it from Xubuntu 18.04 and it will become deprecated.
I guess Debian should drop it too, can't imagine anyone still uses it for
anything (only the Gtk2 parts still work ok).

Cheers
Simon

On Tue, Feb 27, 2018 at 7:53 PM Jeremy Bicha  wrote:

> Control: severity -1 serious
>
> As announced [1], we are working to remove gconf from Debian. As part
> of this process, I am now raising the severity of this bug.
>
> Please try to port your package away from gconf. Otherwise, please
> consider requesting that your package be removed from Debian to help us
> complete this goal.
>
> [1] https://lists.debian.org/debian-devel/2018/02/msg00169.html
>
> On behalf of the Debian GNOME team,
> Jeremy Bicha
>
> --
> xubuntu-devel mailing list
> xubuntu-de...@lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
>

Bug#890064: smbios-utils: properly clean up legacy config files

[Christoph Anton Mitterer]

Hi.

Are you sure this has been fixed properly?

On an upgrade to the new package version I saw:
Unpacking smbios-utils (2.4.1-1) over (2.3.1-2) ...
dpkg: warning: unable to delete old directory '/etc/yum/pluginconf.d': 
Directory not empty
dpkg: warning: unable to delete old directory '/etc/yum': Directory not empty

and while all these are empty, the dirs are still not removed.

Cheers,
Chris.

Bug#891666: xsane: Fix two french translation errors

[Stéphane Blondon]

Package: xsane
Version: 0.999-5
Severity: minor
Tags: patch

There is two errors in the french translation of xsane. The translation
is provided in debian by a specific patch:
0905-i18n_po_update_fr.patch in xsane source package.

In attachment, you can find a patch on 0905-i18n_po_update_fr.patch file
to fix the errors.

Thanks to Yves Moy for catching the main error.
--- 0905-i18n_po_update_fr.patch.orig	2016-04-09 00:56:29.0 +0200
+++ 0905-i18n_po_update_fr.patch	2018-02-27 21:37:49.786182150 +0100
@@ -1065,7 +1065,7 @@
  #. DESC_DISPLAY_ICM_PROFILE
  msgid "Display ICM-profile"
 -msgstr ""
-+msgstr "Affichage du profil ICM"
++msgstr "Profil ICM d'affichage"
  
  #. TEXT_SETUP_CUSTOM_PROOFING_ICM_PROFILE
  #. DESC_CUSTOM_PROOFING_ICM_PROFILE
@@ -2436,7 +2436,7 @@
 -#, fuzzy
  msgid "Browse for printer ICM-profile"
 -msgstr "Parcourir pour un nom d'image"
-+msgstr "Ouvrir un profi ICM d'imprimante"
++msgstr "Ouvrir un profil ICM d'imprimante"
  
  #. DESC_BUTTON_CUSTOM_PROOFING_ICM_PROFILE_BROWSE
 -#, fuzzy


signature.asc
Description: OpenPGP digital signature

Bug#891570: [Bug#891570: SSL connect attempt failed error:141A90B5:SSL routines:ssl_cipher_list_to_bytes:no ciphers available

[Sebastian Andrzej Siewior]

control: clone -1 -2
control: reassign -2 libio-socket-ssl-perl 2.056-1
control: severity -2 normal
control: tags -2 patch

On 2018-02-27 21:52:23 [+0800], 積丹尼 Dan Jacobson wrote:
> Here is all you need to reproduce it:
> 
> $ mech-dump https://mbasic.facebook.com/
> POST 
> https://mbasic.facebook.com/login.php?refsrc=https%3A%2F%2Fmbasic.facebook.com%2F=100=8
> 
> Now  upgrade libssl1.1:amd64 1.1.0g-2 1.1.1~~pre1-1
> 
> $ mech-dump https://mbasic.facebook.com/
> Error GETing https://mbasic.facebook.com/: Can't connect to 
> mbasic.facebook.com:443 (SSL connect attempt failed error:141A90B5:SSL 
> routines:ssl_cipher_list_to_bytes:no ciphers available) at /usr/bin/mech-dump 
> line 68.
> $ dlocate mech-dump
> libwww-mechanize-perl: /usr/bin/mech-dump

Thank you. This was helpfull.
The problem is that libio-socket-ssl-perl has a predefined cipher list
which does not include any TLS1.3 cipher (yes, it has its own). The
patch attached adds TLS1.3 cipher which means that it is possible to
negotiate a TLS1.3 connection if the remote side supports it.

I cloned the bug and hope that openssl falls back to TLS1.2 only
connection if the ciphers are missing especially if the remote side does
not support 1.3. Lets see about that…

Sebastian
diff --git a/lib/IO/Socket/SSL.pm b/lib/IO/Socket/SSL.pm
index ac56aaad4035..8544811d16d6 100644
--- a/lib/IO/Socket/SSL.pm
+++ b/lib/IO/Socket/SSL.pm
@@ -149,6 +149,11 @@ my %DEFAULT_SSL_CLIENT_ARGS = (
 
 SSL_cipher_list => join(" ",
 
+	'TLS13-CHACHA20-POLY1305-SHA256',
+	'TLS13-AES-256-GCM-SHA384',
+	'TLS13-AES-128-GCM-SHA256',
+	'TLS13-AES-128-CCM-8-SHA256',
+	'TLS13-AES-128-CCM-SHA256',
 	# SSLabs report for Chrome 48/OSX. 
 	# This also includes the fewer ciphers Firefox uses.
 	'ECDHE-ECDSA-AES128-GCM-SHA256',

Bug#882103: stretch update for obfsproxy

[Adrian Bunk]

On Thu, Nov 23, 2017 at 07:21:11PM +, Debian Bug Tracking System wrote:
>...
>  obfsproxy (0.2.13-3) unstable; urgency=medium
>...
>* Don't install the AppArmor profile and remove it from disk
>  unless the user has modified it (Closes: #882103)
>...

Thanks a lot for fixing this bug in unstable.

Could you also fix it in stretch?
Unless I misunderstand it the AppArmor profile is also broken there,
and might cause problems during stretch -> buster upgrades.

Alternatively, I can fix it for stretch if you don't object.

Thanks
Adrian

-- 

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

Bug#891664: /usr/bin/mk-build-deps: [mk-build-deps] Doesn't honor Build-Depends-Arch

[Uwe Kleine-König]

Package: devscripts
Version: 2.17.12
Severity: normal
File: /usr/bin/mk-build-deps

Hello,

after

$ mk-build-deps -ris sudo linux

I have:

~$ dpkg -s linux-build-deps
Package: linux-build-deps
Status: install ok installed
Priority: optional
Section: devel
Installed-Size: 9
Maintainer: Uwe Kleine-König 
Architecture: all
Multi-Arch: foreign
Version: 4.15.4-1
Depends: build-essential:amd64, debhelper (>= 10.1~), dh-exec, 
python3:any, quilt, cpio, xz-utils, dh-python, patchutils, graphviz, 
python-sphinx, python-sphinx-rtd-theme
Description: build-dependencies for linux
 Dependency package to build the 'linux' package

This however isn't sufficient to build the linux package:

~/debsrc/linux$ dpkg-buildpackage 
dpkg-buildpackage: info: source package linux
dpkg-buildpackage: info: source version 4.15.4-2
dpkg-buildpackage: info: source distribution UNRELEASED
dpkg-buildpackage: info: source changed by Uwe Kleine-König 

dpkg-buildpackage: info: host architecture amd64
 dpkg-source --before-build linux
dpkg-source: info: using options from 
linux/debian/source/local-options: --abort-on-upstream-changes
dpkg-source: info: using options from linux/debian/source/options: 
--compression=xz --tar-ignore=debian/*.local
dpkg-checkbuilddeps: error: Unmet build dependencies: asciidoc-base 
xmlto libaudit-dev libbabeltrace-dev (>= 1.5.0) libbabeltrace-dev (>= 1.5.3-2~) 
| libbabeltrace-ctf-dev (>= 1.5.0) libdw-dev libelf-dev libiberty-dev 
libnewt-dev libnuma-dev libperl-dev libunwind8-dev libudev-dev libwrap0-dev 
libpci-dev
dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; 
aborting
dpkg-buildpackage: warning: (Use -d flag to override.)

The problem is that mk-build-deps didn't pick up the packages listed in
Build-Depends-Arch:, only those from Build-Depends (and optionally
Build-Depends-Indep).

The following patch helped me, but I don't dare to tag this bug with "patch" as
I'm not confident enough in my perl and debian-package skills. Also I think
mk-build-deps should also handle Build-Conflicts-Indep.

Best regards
Uwe

diff --git a/scripts/mk-build-deps.pl b/scripts/mk-build-deps.pl
index 261238975699..a0ab3fd7 100755
--- a/scripts/mk-build-deps.pl
+++ b/scripts/mk-build-deps.pl
@@ -275,7 +275,7 @@ while ($control = shift) {
}
my $args = '';
my $arch = 'all';
-   my ($build_deps, $build_dep, $build_indep);
+   my ($build_deps, $build_dep, $build_arch, $build_indep);
my ($build_conflicts, $conflict_arch, $conflict_indep);
 
if (exists $ctrl->{'Build-Depends'}) {
@@ -283,6 +283,14 @@ while ($control = shift) {
$build_dep =~ s/\n/ /g;
$build_deps = $build_dep;
}
+   if (exists $ctrl->{'Build-Depends-Arch'}) {
+   $build_arch = $ctrl->{'Build-Depends-Arch'};
+   $build_arch =~ s/\n/ /g;
+   $build_dep .= ', ' if $build_dep;
+   $build_dep .= $build_arch;
+   $build_deps .= ', ' if $build_deps;
+   $build_deps .= $build_arch;
+   }
if (exists $ctrl->{'Build-Depends-Indep'}) {
$build_indep = $ctrl->{'Build-Depends-Indep'};
$build_indep =~ s/\n/ /g;

Bug#862531: stretch update for nbd

[Adrian Bunk]

On Wed, Sep 13, 2017 at 03:12:07PM +, Debian Bug Tracking System wrote:
>...
>  nbd (1:3.16.2-1) unstable; urgency=medium
>...
>* Add missing After=network-online.target to nbd@ systemd unit.
>  Closes: #862531.
>...

Thanks a lot for fixing this bug for unstable.

It is still present in stretch, could you also fix it there?
Alternatively, I can fix it for stretch if you don't object.

Thanks
Adrian

-- 

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

Bug#891663: [PATCH] libgpg-error: Add support for the riscv64 architecture

[Karsten Merker]

Source: libgpg-error
Version: 1.27-6
X-Debbugs-CC: debian-ri...@lists.debian.org
Tags: patch
Severity: wishlist
User: debian-ri...@lists.debian.org
Usertags: riscv64

Hello,

we are in the process of bootstrapping a Debian port for the
riscv64 architecture (https://wiki.debian.org/RISC-V).  The
libgpg-error package is part of the build-dependency chain for
the essential package set, so we need to build it for riscv64 to
be able to complete the bootstrap process.

AIUI, libgpg-error requires a per-architecture header file
"src/syscfg/lock-obj-pub..h", which upstream doesn't
provide for riscv64.  Based on the information in the header
files for the other architectures, I have created such a file for
riscv64 by cross-building and executing (in qemu) the
gen-posix-lock-obj helper program:

$ riscv64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I../../src -I..   -Wdate-time 
-D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/usr/src/repositories/libgpg-error=. 
-specs=/usr/share/dpkg/pie-compile.specs -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -Wpointer-arith -Wno-psabi -fvisibility=hidden -c 
-o gen-posix-lock-obj.o ../../src/gen-posix-lock-obj.c
$ /bin/bash ../libtool  --tag=CC   --mode=link riscv64-linux-gnu-gcc  -g -O2 
-fdebug-prefix-map=/usr/src/repositories/libgpg-error=. 
-specs=/usr/share/dpkg/pie-compile.specs -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -Wpointer-arith -Wno-psabi -fvisibility=hidden  
-specs=/usr/share/dpkg/pie-link.specs -Wl,-z,relro -Wl,-z,now -o 
gen-posix-lock-obj gen-posix-lock-obj.o
libtool: link: riscv64-linux-gnu-gcc -g -O2 
-fdebug-prefix-map=/usr/src/repositories/libgpg-error=. 
-specs=/usr/share/dpkg/pie-compile.specs -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -Wpointer-arith -Wno-psabi -fvisibility=hidden 
-specs=/usr/share/dpkg/pie-link.specs -Wl,-z -Wl,relro -Wl,-z -Wl,now -o 
gen-posix-lock-obj gen-posix-lock-obj.o
$ ./gen-posix-lock-obj   # (executed in qemu via binfmt-misc)
## lock-obj-pub.riscv64-unknown-linux-gnu.h
## File created by gen-posix-lock-obj - DO NOT EDIT
## To be included by mkheader into gpg-error.h

typedef struct
{
  long _vers;
  union {
volatile char _priv[40];
long _x_align;
long *_xp_align;
  } u;
} gpgrt_lock_t;

#define GPGRT_LOCK_INITIALIZER {1,{{0,0,0,0,0,0,0,0, \
0,0,0,0,0,0,0,0, \
0,0,0,0,0,0,0,0, \
0,0,0,0,0,0,0,0, \
0,0,0,0,0,0,0,0}}}
##
## Local Variables:
## mode: c
## buffer-read-only: t
## End:
##

Attached is the raw header file as well as a patch for the
packaging to carry this header file as a Debian patch.  I would
apprechiate very much if you could upload a new package version
that includes this patch to unstable in the near future as we
depend on it for continuing our bootstrap efforts.

Regards,
Karsten
-- 
Gem. Par. 28 Abs. 4 Bundesdatenschutzgesetz widerspreche ich der Nutzung
sowie der Weitergabe meiner personenbezogenen Daten für Zwecke der
Werbung sowie der Markt- oder Meinungsforschung.
## lock-obj-pub.riscv64-unknown-linux-gnu.h
## File created by gen-posix-lock-obj - DO NOT EDIT
## To be included by mkheader into gpg-error.h

typedef struct
{
  long _vers;
  union {
volatile char _priv[40];
long _x_align;
long *_xp_align;
  } u;
} gpgrt_lock_t;

#define GPGRT_LOCK_INITIALIZER {1,{{0,0,0,0,0,0,0,0, \
0,0,0,0,0,0,0,0, \
0,0,0,0,0,0,0,0, \
0,0,0,0,0,0,0,0, \
0,0,0,0,0,0,0,0}}}
##
## Local Variables:
## mode: c
## buffer-read-only: t
## End:
##
>From cec778b68abe56de49f838af5754348494778abe Mon Sep 17 00:00:00 2001
From: Karsten Merker 
Date: Tue, 27 Feb 2018 19:43:09 +
Subject: [PATCH] add riscv64-unknown-linux-gnu lock-obj definitions

---
 ...bj-pub-file-for-riscv64-unknown-linux-gnu.patch | 30 ++
 debian/patches/series  |  1 +
 2 files changed, 31 insertions(+)
 create mode 100644 debian/patches/0017-syscfg-Add-lock-obj-pub-file-for-riscv64-unknown-linux-gnu.patch

diff --git a/debian/patches/0017-syscfg-Add-lock-obj-pub-file-for-riscv64-unknown-linux-gnu.patch b/debian/patches/0017-syscfg-Add-lock-obj-pub-file-for-riscv64-unknown-linux-gnu.patch
new file mode 100644
index 000..19ec11a
--- /dev/null
+++ b/debian/patches/0017-syscfg-Add-lock-obj-pub-file-for-riscv64-unknown-linux-gnu.patch
@@ -0,0 +1,30 @@
+Index: libgpg-error/src/syscfg/lock-obj-pub.riscv64-unknown-linux-gnu.h
+===
+--- /dev/null
 libgpg-error/src/syscfg/lock-obj-pub.riscv64-unknown-linux-gnu.h
+@@ -0,0 +1,25 @@
++## lock-obj-pub.riscv64-unknown-linux-gnu.h
++## File created by gen-posix-lock-obj - DO NOT EDIT
++## To be included by mkheader into