Bug#866308: qtkeychain 0.8 fails to use kwallet5

[Sandro Knauß]

Source: qtkeychain
Version: 0.8.0-1
Severity: normal
Tags: upstream
Control: forwarded -1 https://github.com/frankosterfeld/qtkeychain/issues/99

Hey,

because building qtkeychain with libsecrect1 makes it impossible to use
qtkeychain in a kde environment, we should not update qtkeychain till it
gets updated.

Best regards,

sandro


-- System Information:
Debian Release: 9.0
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'unstable'), (500, 'testing'), 
(500, 'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Bug#866082: Fails on Guided partitioning for 8GiB disk

[Ben Hutchings]

On Wed, 2017-06-28 at 08:39 +0200, Narcis Garcia wrote:
> Many people may feel this matter is not important because most of
> installations are for traditional PCs, but there are other scenarios
> such as TV devices, phone/tablets, VM, etc. with less internal space.

Debian installer is not intended for setting up embedded systems.

Ben.

-- 
Ben Hutchings
Absolutum obsoletum. (If it works, it's out of date.) - Stafford Beer



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

Bug#866126: nvidia-detect: fails to identify Debian suite (buster/sid)

[Alexandre Hoïde]

On Tue, Jun 27, 2017 at 10:41:56PM +0100, Luca Boccassi wrote:
> Control: tags -1 pending
> 
> On Tue, 2017-06-27 at 17:53 +0200, Alexandre Hoïde wrote:
> > Package: nvidia-detect
> > Version: 375.66-2
> > Severity: important
> > 
> > Dear Maintainer,
> > 
> > On a buster/sid system, nvidia-detect fails with : "Uh oh. Failed to
> > identify your Debian suite."
> > 
> > Regards,
> > Alexandre Hoïde
> 
> Thanks for the report, fixed in SVN pending the next upload.
> 
> If you need the fix urgently it's pretty simple to apply locally:
> 
> https://anonscm.debian.org/viewvc/pkg-nvidia/packages/nvidia-graphics-drivers/trunk/debian/detect/nvidia-detect.in?r1=7307=7306=7307
> 
> Kind regards,
> Luca Boccassi

Thank you Luca. Applied and working as expected. I'll check if the bug
needs to be closed when it reaches sid archives.

Best regards,
Alexandre Hoïde

Bug#866306: haveged fails to start with linux 4.12 on an Odroid-C2

[Vagrant Cascadian]

Package: haveged
Version: 1.9.1-5
Severity: normal
X-Debbugs-Cc: debian-...@lists.debian.org

I've been trying to set up an Odroid-C2 for the Debian reproducible
builds test infrastructure, but haveged fails to start on this
particular machine with linux kernel 4.12. I've tried running the same
4.12 kernels on other boards (pine64+) and haveged works fine.

With linux 4.11 haveged works fine on this board as well. Unfortunately,
the eMMC used for rootfs and other filesystems isn't recognized by linux
4.11...

When I try with an armhf userspace and linux 4.12, haveged actually
segfaults.

Are there any particular kernel options required for haveged to work
correctly? Any other ideas for troubleshooting?

I can work around the issue using rngd to get randomness, as it has a
hardware random number generator, but I'm wondering if this is a bug
specific to haveged, or if this indicates of other problems that would
impact other software...


With arm64 userspace it just fails:

$ sudo strace -o haveged.strace.log  haveged --Foreground --verbose=-1 --file 
data
haveged: Address 0=0xb42b1fdc
haveged: Address 1=0xb42b1a54
haveged: Loop 1: offset=70644, delta=1416
haveged: Address 2=0xb42b12d0
haveged: Loop 2: offset=68720, delta=1924
haveged: Address 3=0xb42b0b4c
haveged: Loop 3: offset=66796, delta=1924
haveged: Address 4=0xb42b03c8
haveged: Loop 4: offset=64872, delta=1924
haveged: Address 5=0xb42afc44
haveged: Loop 5: offset=62948, delta=1924
haveged: Address 6=0xb42af4c0
haveged: Loop 6: offset=61024, delta=1924
haveged: Address 7=0xb42aed3c
haveged: Loop 7: offset=59100, delta=1924
haveged: Address 8=0xb42ae5b8
haveged: Loop 8: offset=57176, delta=1924
haveged: Address 9=0xb42ade34
haveged: Loop 9: offset=55252, delta=1924
haveged: Address 10=0xb42ad6b0
haveged: Loop 10: offset=53328, delta=1924
haveged: Address 11=0xb42acf2c
haveged: Loop 11: offset=51404, delta=1924
haveged: Address 12=0xb42ac7a8
haveged: Loop 12: offset=49480, delta=1924
haveged: Address 13=0xb42ac024
haveged: Loop 13: offset=47556, delta=1924
haveged: Address 14=0xb42ab8a0
haveged: Loop 14: offset=45632, delta=1924
haveged: Address 15=0xb42ab11c
haveged: Loop 15: offset=43708, delta=1924
haveged: Address 16=0xb42aa998
haveged: Loop 16: offset=41784, delta=1924
haveged: Address 17=0xb42aa214
haveged: Loop 17: offset=39860, delta=1924
haveged: Address 18=0xb42a9a90
haveged: Loop 18: offset=37936, delta=1924
haveged: Address 19=0xb42a930c
haveged: Loop 19: offset=36012, delta=1924
haveged: Address 20=0xb42a8b88
haveged: Loop 20: offset=34088, delta=1924
haveged: Address 21=0xb42a8404
haveged: Loop 21: offset=32164, delta=1924
haveged: Address 22=0xb42a7c80
haveged: Loop 22: offset=30240, delta=1924
haveged: Address 23=0xb42a74fc
haveged: Loop 23: offset=28316, delta=1924
haveged: Address 24=0xb42a6d78
haveged: Loop 24: offset=26392, delta=1924
haveged: Address 25=0xb42a65f4
haveged: Loop 25: offset=24468, delta=1924
haveged: Address 26=0xb42a5e70
haveged: Loop 26: offset=22544, delta=1924
haveged: Address 27=0xb42a56ec
haveged: Loop 27: offset=20620, delta=1924
haveged: Address 28=0xb42a4f68
haveged: Loop 28: offset=18696, delta=1924
haveged: Address 29=0xb42a4918
haveged: Loop 29: offset=17080, delta=1616
haveged: Address 30=0xb42a42c8
haveged: Loop 30: offset=15464, delta=1616
haveged: Address 31=0xb42a3c78
haveged: Loop 31: offset=13848, delta=1616
haveged: Address 32=0xb42a3608
haveged: Loop 32: offset=12200, delta=1648
haveged: Address 33=0xb42a2fb8
haveged: Loop 33: offset=10584, delta=1616
haveged: Address 34=0xb42a2968
haveged: Loop 34: offset=8968, delta=1616
haveged: Address 35=0xb42a2318
haveged: Loop 35: offset=7352, delta=1616
haveged: Address 36=0xb42a1cc8
haveged: Loop 36: offset=5736, delta=1616
haveged: Address 37=0xb42a1678
haveged: Loop 37: offset=4120, delta=1616
haveged: Address 38=0xb42a111c
haveged: Loop 38: offset=2748, delta=1372
haveged: Address 39=0xb42a0bc0
haveged: Loop 39: offset=1376, delta=1372
haveged: Address 40=0xb42a0660
haveged: Loop 40: offset=0, delta=1376
haveged starting up
haveged: Couldn't initialize HAVEGE rng 5

Which produces haveged.strace.log:

execve("/usr/sbin/haveged", ["haveged", "--Foreground", "--verbose=-1", 
"--file", "data"], [/* 14 vars */]) = 0
brk(NULL)   = 0xd2d82000
faccessat(AT_FDCWD, "/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or 
directory)
mmap(NULL, 12288, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0xb42ef000
faccessat(AT_FDCWD, "/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or 
directory)
openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=28891, ...}) = 0
mmap(NULL, 28891, PROT_READ, MAP_PRIVATE, 3, 0) = 0xb42e7000
close(3)= 0
faccessat(AT_FDCWD, 

Bug#866307: Play it safe: comment out SIGKILL (-9) in default and.priorities(5)

[Ivan Shmakov]

Package:  and
Version:  1.2.2-4.1+b2

It does not seem like a good idea to have and(8) send SIGKILL
to /any/ processes by default – not even to ones named ‘gcc’ and
which run for 20 minutes.

Thus, I believe that the respective lines in the default
and.priorities(5) file should be commented out.

-- 
FSF associate member #7257  58F8 0F47 53F5 2EB2 F6A5  8916 3013 B6A0 230E 334A

Bug#865242: [Pkg-lyx-devel] Bug#865242: Please update dependencies from latex-xcolor to tl-latex-recommended

[Sven Hoexter]

On Tue, Jun 20, 2017 at 02:05:00PM +0900, norb...@preining.info wrote:

Hi,

> latex-xcolor has been a dummy transitional package now since 2 releases
> (since oldstable), and has been dropped in current unstable.
> 
> Please update your dependencies to texlive-latex-recommended.

Thanks Norbert, commited & pushed the change to git. Should hit the
archive with the next upload, though that might take a while.
Since we already recommend texlive-latex-recommended for while that
issue should not hurt users, might just confuse someone.

Sven

Bug#866257: tpm2-tools: CVE-2017-7524

[Salvatore Bonaccorso]

Source: tpm2-tools
Version: 1.1-1
Severity: important
Tags: security upstream patch

Hi,

the following vulnerability was published for tpm2-tools.

CVE-2017-7524[0]:
| tpm2-tools versions before 1.1.1 are vulnerable to a password leak due
| to transmitting password in plaintext from client to server when
| generating HMAC.

The code evolved quite a bit after
462f35ad5de538cf5961806918a18c22add92c00 upstream, but the issue
should be present back and before there in the source.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-7524
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-7524
[1] 
https://github.com/01org/tpm2.0-tools/commit/c5d72beaab1cbbbe68271f4bc4b6670d69985157

Regards,
Salvatore

Bug#866256: Add lxqt-policykit as dependency and lxqt-qtplugin as recommend

[Alf Gaida]

Package: lxqt-powermanagement
Version: 0.11.3~26-g05c20ce-1
Severity: normal
Tags: newcomer

lxqt-policykit will be needed for device operations.
lxqt-qtplugin should be at least recommended to pick up session settings.

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

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

Versions of packages lxqt-powermanagement depends on:
ii  libc62.24-12
ii  libkf5idletime5  5.28.0-1
ii  libkf5solid5 5.28.0-4
ii  liblxqt0 0.11.2~13-g05e4153
ii  libqt5core5a 5.7.1+dfsg-3+b1
ii  libqt5dbus5  5.7.1+dfsg-3+b1
ii  libqt5gui5   5.7.1+dfsg-3+b1
ii  libqt5svg5   5.7.1~20161021-2+b2
ii  libqt5widgets5   5.7.1+dfsg-3+b1
ii  libqt5xdg2   2.0.1~54-g075f9f4-1
ii  libstdc++6   7.1.0-7

Versions of packages lxqt-powermanagement recommends:
ii  lxqt-powermanagement-l10n  0.11.3~31-g70dd9ff4~1
ii  upower 0.99.4-4+b1

lxqt-powermanagement suggests no packages.

-- no debconf information

Bug#854210: libnet-xmpp-perl: sendxmpp can't send message to hangouts (work fine for 1.02-5)

[gregor herrmann]

Control: reassign -1 sendxmpp 1.23-1.1
Control: severity -1 important
Control: retitle -1 sendxmpp: sendxmpp can't send message with TLS/SSL without 
passing -tls-ca-path

On Wed, 28 Jun 2017 00:09:12 +0200, Markus Gschwendt wrote:

> > > Maybe I miss something obvious, but IMHO the bug should 1/ be
> > > reassigned to sendxmpp itself. Then the question is if sendxmpp
> > > should
> > > be patches actually (if so it might need to depend on
> > > ca-certificates), or "just" document when
> > > -tls-ca-path="/etc/ssl/certs" needs to be passed.
> If people don't like to use SSL (which i would consider as a bad idea
> these days) they also don't want a dependency on ca-certificates. So it
> should be a 'reccomended package'.

I think that's not really an option, as what we are seeing here, and
that's the start of the bug report, is tjat there are servers which
enforce TLS/SSL.
(But maybe I'm wrong here.)
 
> > Ack, AFAICS Net::XMPP fixed a bug (ignoring the path to the certs)
> > and this triggered the necessity for sendxmpp to set it (by the user
> > or in the code). 
> I'd like to have the default set in Net::XMPP debian package to have it
> available in several applications which use this library.

I don't see a place of/for default values there, and I still think
it's the wrong place.

Net::XMPP::Connection offers a Connect() method (which is used by
sendxmpp [0]) which optionally offers to set some TLS/SSL parameters.
They can also be left out but saying "yes we want TLS/SSL but we
don't tell you were to find the certs", as sendxmpp does, breaks
later in the underlying XML::Stream.

Or in other words: I think sendxmpp is just using
Net::XMPP::Connection wrong.

> Maybe in sendxmpp too.

I'm still sure that it belongs there because it is sendxmpp which
sets tls-ca-path explicitly to an empty value which then causes
havoc.

BTW, in the meantime I think it belongs in line
80   $$cmdline{'tls-ca-path'} || $$config{'tls-ca-path'} || 
'/etc/ssl/certs',

Alternatively, just dropping the empty string seems to work too:
80   $$cmdline{'tls-ca-path'} || $$config{'tls-ca-path'},


Conclusion:
So far we only see problems with sendxmpp; sendxmpp is not broken
(manually setting the parameters works) but is sub-optimal: it would
profit from either setting a default path or not setting an empty
path (!). And the fix is easy as well.

Therefore I'm now reassigning the bug to sendxmpp and lowering the
severity.


Cheers,
gregor


[0]
Arguably a bad idea, as that's an internal module according to its
documentation but anyway.

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


signature.asc
Description: Digital Signature

Bug#866255: lxqt-panel should recommend lxqt-qtplugin

[Alf Gaida]

Package: lxqt-panel
Version: 0.11.2~60-g68e866a2-1
Severity: normal
Tags: newcomer

lxqt-qtplugin is needed to pick up the settings from the session.
It should be at least recommended.


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

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

Versions of packages lxqt-panel depends on:
ii  libasound2  1.1.3-5
ii  libc6   2.24-12
ii  libdbusmenu-qt5-2   0.9.3+16.04.20160218-1
ii  libglib2.0-02.52.3-1
ii  libkf5solid55.28.0-4
ii  libkf5windowsystem5 5.28.0-2
ii  liblxqt-globalkeys-ui0  0.11.2~36-g9e64d65-1
ii  liblxqt-globalkeys0 0.11.2~36-g9e64d65-1
ii  liblxqt00.11.2~13-g05e4153
ii  libmenu-cache3  1.0.3~7-g4695338-1
ii  libpulse0   10.0-2
ii  libqt5core5a5.7.1+dfsg-3+b1
ii  libqt5dbus5 5.7.1+dfsg-3+b1
ii  libqt5gui5  5.7.1+dfsg-3+b1
ii  libqt5widgets5  5.7.1+dfsg-3+b1
ii  libqt5x11extras55.7.1~20161021-2
ii  libqt5xdg2  2.0.1~54-g075f9f4-1
ii  libqt5xml5  5.7.1+dfsg-3+b1
ii  libsensors4 1:3.4.0-4
ii  libstatgrab10   0.91-1+b1
ii  libstdc++6  7.1.0-7
ii  libsysstat-qt5-00.3.4~2-g43d8f4d-1
ii  libx11-62:1.6.4-3
ii  libxcb-xkb1 1.12-1
ii  libxcb1 1.12-1
ii  libxcomposite1  1:0.4.4-2
ii  libxdamage1 1:1.1.4-2+b3
ii  libxkbcommon-x11-0  0.7.1-1
ii  libxkbcommon0   0.7.1-1
ii  libxrender1 1:0.9.10-1
ii  lxmenu-data 0.1.5-2

Versions of packages lxqt-panel recommends:
ii  lxqt-panel-l10n  0.11.3~31-g70dd9ff4~1

lxqt-panel suggests no packages.

-- no debconf information

Bug#866254: lxqt-openssh-askpass should recommend lxqt-qtplugin

[Alf Gaida]

Package: lxqt-openssh-askpass
Version: 0.11.2~3-g1ffc056-1
Severity: normal
Tags: newcomer

lxqt-qtplugin is needed to pick up the settings from the session.
It should be at least recommend.


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

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

Versions of packages lxqt-openssh-askpass depends on:
ii  libc6   2.24-12
ii  liblxqt00.11.2~13-g05e4153
ii  libqt5core5a5.7.1+dfsg-3+b1
ii  libqt5widgets5  5.7.1+dfsg-3+b1
ii  libstdc++6  7.1.0-7

Versions of packages lxqt-openssh-askpass recommends:
ii  lxqt-openssh-askpass-l10n  0.11.3~31-g70dd9ff4~1

lxqt-openssh-askpass suggests no packages.

-- no debconf information

Bug#866253: lxqt-notificationd should recommend lxqt-qtplugin

[Alf Gaida]

Package: lxqt-notificationd
Version: 0.11.2~19-g84cfff0-1
Severity: normal
Tags: newcomer

lxqt-qtplugin is needed to pick up the settings from the session.
It should be at least recommended.


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

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

Versions of packages lxqt-notificationd depends on:
ii  libc62.24-12
ii  libkf5windowsystem5  5.28.0-2
ii  liblxqt0 0.11.2~13-g05e4153
ii  libqt5core5a 5.7.1+dfsg-3+b1
ii  libqt5dbus5  5.7.1+dfsg-3+b1
ii  libqt5gui5   5.7.1+dfsg-3+b1
ii  libqt5widgets5   5.7.1+dfsg-3+b1
ii  libqt5xdg2   2.0.1~54-g075f9f4-1
ii  libstdc++6   7.1.0-7

Versions of packages lxqt-notificationd recommends:
ii  lxqt-notificationd-l10n  0.11.3~31-g70dd9ff4~1

lxqt-notificationd suggests no packages.

-- no debconf information

Bug#866085: At least it should be the option to not download

[Narcis Garcia]

> 
> If you are doing an install party, set up a proxy server.  That really
> really helps a lot.
> 

Not only experts should be able to do an install party; some more people
wants to share small knowledge and experiences.

Bug#850291: gdm3: does not work without gnome-session

[Michael Biebl]

Control: severity -1 serious

On Thu, 5 Jan 2017 13:33:21 -0500 Daniel Gnoutcheff
 wrote:
> Package: gdm3
> Version: 3.22.1-1
> Severity: normal
> 
> If I try to run gdm3 while gnome-session is not installed, the greeter
> will not come up.  It instead blanks and unblanks the screen repeatedly,
> presumably as it keeps respawning the greeter.  Installing gnome-session
> fixes it.
> 
> It sounds like gnome-session-bin was supposed to be sufficient, but
> apparently it isn't at the moment.
> 

Marking this as RC (missing dependency to function properly).
We should fix that in stretch via a point release.



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#866246: jdupes -B fails to fully deduplicate large (> 16 MiB) files

[Ivan Shmakov]

Package:  jdupes
Version:  1.7-2
Severity: minor

As currently implemented, jdupes(1) invokes FIDEDUPERANGE once
for each set of files found to be duplicates.  However, per
documentation (say, [1]), there can be a filesystem-specific
limit in place on how large a data span can be handled in a
single call to FIDEDUPERANGE.  Per strace(1) output, this limit
appears to indeed be 16 MiB for Btrfs on Debian Stretch.

An obvious solution is to get the maximum of the bytes_deduped
values returned by the call and invoke it again, advancing
src_offset and dest_offset values by that maximum, possibly
repeating these steps until the whole file length is covered.

AFAICT, this issue is not solved as of recent Git (a32de0db,
2017-06-07.)

[1] http://man7.org/linux/man-pages/man2/ioctl_fideduperange.2.html

-- 
FSF associate member #7257  58F8 0F47 53F5 2EB2 F6A5  8916 3013 B6A0 230E 334A

Bug#866245: dokuwiki: Invalid argument supplied for foreach() /usr/share/dokuwiki/lib/exe/js.php

[SATOH Fumiyasu]

Package: dokuwiki
Version: 0.0.20160626.a-2
Severity: normal

debian/add-ons/preload.php must be updated for newer DokuWiki release
that includes the following changes:

* Extendable config cascade for userstyles and userscript by Klap-in · Pull 
Request #954 · splitbrain/dokuwiki
* https://github.com/splitbrain/dokuwiki/pull/954/files

--- debian/add-ons/preload.php.dist 2016-02-25 23:02:29.0 +0900
+++ debian/add-ons/preload.php  2017-06-29 03:49:44.269455964 +0900
@@ -138,14 +138,14 @@
 'default'   => DOKU_CONF.'users.auth.php',
 ),
 'userstyle' => array(
-'default' => DOKU_CONF.'userstyle.css', // 'default' was renamed to 
'screen' on 2011-02-26, so will be deprecated in the next version
-'screen'  => DOKU_CONF.'userstyle.css',
-'rtl' => DOKU_CONF.'userrtl.css',
-'print'   => DOKU_CONF.'userprint.css',
-'feed'=> DOKU_CONF.'userfeed.css',
-'all' => DOKU_CONF.'userall.css',
+'default' => array(DOKU_CONF.'userstyle.css'), // 'default' was 
renamed to 'screen' on 2011-02-26, so will be deprecated in the next version
+'screen'  => array(DOKU_CONF.'userstyle.css'),
+'rtl' => array(DOKU_CONF.'userrtl.css'),
+'print'   => array(DOKU_CONF.'userprint.css'),
+'feed'=> array(DOKU_CONF.'userfeed.css'),
+'all' => array(DOKU_CONF.'userall.css'),
 ),
 'userscript' => array(
-'default' => DOKU_CONF.'userscript.js'
+'default' => array(DOKU_CONF.'userscript.js')
 ),
 );

See also:

* Invalid argument supplied for foreach() /usr/share/dokuwiki/lib/exe/js.php · 
Issue #1726 · splitbrain/dokuwiki
* https://github.com/splitbrain/dokuwiki/issues/1726
* Invalid argument supplied for foreach() · Issue #1664 · splitbrain/dokuwiki
* https://github.com/splitbrain/dokuwiki/issues/1664

Regards,

-- 
-- Name: SATOH Fumiyasu @ OSS Technology Corp. (fumiyas @ osstech co jp)
-- Business Home: http://www.OSSTech.co.jp/
-- GitHub Home: https://GitHub.com/fumiyas/
-- PGP Fingerprint: BBE1 A1C9 525A 292E 6729  CDEC ADC2 9DCA 5E1C CBCA

Bug#866083: Default GRUB install target should be hard disk

[Ben Hildred]

On Wed, Jun 28, 2017 at 12:34 AM, Narcis Garcia 
wrote:

> When user selects to (yes) install boot manager, the wizard asks where
> to do the grub-install.
> Currently, default option in the dialog is to introduce manually the
> target path. I propose to change default option by the already detected
> path.
>
>
Also note that this change will aid in preseeding when deploying the same
image to multiple hardware configurations.

-- 
--
Ben Hildred
Automation Support Services
303 815 6721

Bug#866226: systemd 233 breaks docker with "no subsystem for mount" error

[jeroen verellen]

Thank you Laurent, adding the kernel options worked as a charm.
My docker containers are starting again.

Kind regards, Jeroen


On Wed, Jun 28, 2017 at 4:54 PM, Jeroen Verellen 
wrote:

> Package: systemd
> Version: 233-9
> Severity: normal
>
> Dear Maintainer,
>
> I have an issue after the latest update of systemd. It seems to be similar
> as https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843509
>
> When starting a docker container I get the following:
>
> docker start mysql
> Error response from daemon: oci runtime error: container_linux.go:247:
> starting container process caused "process_linux.go:359: container init
> caused \"rootfs_linux.go:54: mounting \\\"cgroup\\\" to rootfs
> \\\"/var/lib/docker/overlay2/177270b60c5ab19437e45fc913e424
> 2b89b8e1ed5913c707563cc9c4850512e2/merged\\\" at \\\"/sys/fs/cgroup\\\"
> caused \\\"no subsystem for mount\\\"\""
> Error: failed to start containers: mysql
>
> Details on docker.io package:
> Package: docker.io
> Versions:
> 1.13.1~ds1-2 
> (/var/lib/apt/lists/ftp.be.debian.org_debian_dists_sid_main_binary-amd64_Packages)
> (/var/lib/dpkg/status)
>  Description Language:
>  File: /var/lib/apt/lists/ftp.be.
> debian.org_debian_dists_sid_main_binary-amd64_Packages
>   MD5: 05dc9eba68f3bf418e6a0cf29d555878
>  Description Language: en
>  File: /var/lib/apt/lists/ftp.be.
> debian.org_debian_dists_sid_main_i18n_Translation-en
>   MD5: 05dc9eba68f3bf418e6a0cf29d555878
>
>
> Reverse Depends:
>   containerd,docker.io 1.12
>   whalebuilder,docker.io
>   subuser,docker.io
>   runc,docker.io 1.12
>   ruby-docker-api,docker.io
>   packer,docker.io
>   libnss-docker,docker.io
>   kubernetes-node,docker.io
>   golang-libnetwork,docker.io 1.12
>   gitlab-ci-multi-runner,docker.io
>   vim-syntax-docker,docker.io
>   docker-compose,docker.io 1.9.0
>   debocker,docker.io
>   cockpit-docker,docker.io 1.3.0
> Dependencies:
> 1.13.1~ds1-2 - adduser (0 (null)) containerd (2
> 0.2.3+git20170126.85.aa8187d~ds1~) iptables (0 (null)) golang-libnetwork
> (2 0.8.0-dev.2+git20170202.599.45b4086~) lsb-base (0 (null)) runc (2
> 1.0.0~rc2+git20170201.133.9df8b30~) init-system-helpers (2 1.18~)
> libapparmor1 (2 2.6~devel) libc6 (2 2.17) libdevmapper1.02.1 (2 2:1.02.97)
> libsqlite3-0 (2 3.7.15) libsystemd0 (0 (null)) docker (3 1.5~)
> ca-certificates (0 (null)) cgroupfs-mount (16 (null)) cgroup-lite (0
> (null)) git (0 (null)) xz-utils (0 (null)) aufs-tools (0 (null))
> btrfs-progs (0 (null)) debootstrap (0 (null)) docker-doc (0 (null)) rinse
> (0 (null)) zfs-fuse (16 (null)) zfsutils (0 (null)) docker (3 1.5~)
> Provides:
> 1.13.1~ds1-2 -
> Reverse Provides:
>
>
> -- Package-specific info:
>
> -- System Information:
> Debian Release: buster/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 4.9.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 /bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages systemd depends on:
> ii  adduser 3.115
> ii  libacl1 2.2.52-3+b1
> ii  libapparmor12.11.0-5
> ii  libaudit1   1:2.7.7-1
> ii  libblkid1   2.29.2-1
> ii  libc6   2.24-12
> ii  libcap2 1:2.25-1
> ii  libcryptsetup4  2:1.7.3-4
> ii  libgcrypt20 1.7.7-2
> ii  libgpg-error0   1.27-3
> ii  libidn111.33-1
> ii  libip4tc0   1.6.1-1
> ii  libkmod224-1
> ii  liblz4-10.0~r131-2+b1
> ii  liblzma55.2.2-1.2+b1
> ii  libmount1   2.29.2-1
> ii  libpam0g1.1.8-3.6
> ii  libseccomp2 2.3.1-2.1
> ii  libselinux1 2.6-3+b1
> ii  libsystemd0 233-9
> ii  mount   2.29.2-1
> ii  procps  2:3.3.12-3
> ii  util-linux  2.29.2-1
>
> Versions of packages systemd recommends:
> ii  dbus1.10.18-1
> ii  libpam-systemd  233-9
>
> Versions of packages systemd suggests:
> ii  policykit-10.105-18
> pn  systemd-container  
>
> Versions of packages systemd is related to:
> pn  dracut   
> ii  initramfs-tools  0.130
> ii  udev 233-9
>
> -- no debconf information
>

Bug#863049: jessie-pu: package shutter/0.92-0.1+deb8u2

[gregor herrmann]

On Wed, 28 Jun 2017 01:27:42 +0200, Cyril Brulebois wrote:

> gregor herrmann  (2017-05-20):
> > I've prepared an upload of shutter for stable. The new version
> > includes two patches:
> > - one fixing CVE-2016-10081 / #849777
> > - another one which dod uploaded together with this one as 0.93.1-1.3
> >   in January which is also security relevant (replaces
> >   system("string") with system(@array)).
> That's a long patch… Comments below (see last hunk, mainly).

Thanks for taking the time to go through the patch in detail!
 
> > + sub nautilus_sendto {
> > +   my ( $self, $user_data ) = @_;
> > +-  system("nautilus-sendto $user_data &");
> > ++  system('nautilus-sendto', $user_data);
> > +   if($?){
> > +   my $response = $self->{_dialogs}->dlg_error_message( 
> > +   sprintf( $self->{_d}->get("Error while executing %s."), 
> > "'nautilus-sendto'"),
> 
> Was the '&' really meant to go away?

I suppose yes, in order to make sure that the script waits for nautilus-sendto
to return, as the return value is checked in the next line.

And/or because it simply doesn't work, as adding a '&' would be
interpreted as an argument:


#v+
#!/usr/bin/perl

use strict;
use warnings;

my $args='-ls';

print "string\n";
system( "ls $args &" ) == 0 or die "system(string) failed: $?";
#-

% perl background.pl
string
total 4 
  
4 -rw-rw-r-- 1 gregoa gregoa 234 Jun 28 20:10 background.pl


vs.


#v+
#!/usr/bin/perl

use strict;
use warnings;

my $args='-ls';

print "list\n";
system( 'ls', '-la', '&' ) == 0 or die "system(list) failed: $?";
#v-

% perl background.pl
list
ls: cannot access '&': No such file or directory
system(list) failed: 512 at background.pl line 9.


So yes, this seems intended :)


Nevertheless looping in dod as the author of this patch.


Cheers,
gregor


-- 
 .''`.  https://info.comodo.priv.at/ - Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Ben Weaver: Voice In The Wilderness


signature.asc
Description: Digital Signature

Bug#866243: xfce4-goodies: Please, include the xfce4-time-out-plugin

[jEsuSdA]

Package: xfce4-goodies
Version: 4.12.3
Severity: wishlist

Dear Maintainer,

I want to suggest you to include the Time Out plugin in the repository.

http://goodies.xfce.org/projects/panel-plugins/xfce4-time-out-plugin

It is an useful plugin and I must to install it from ubuntu packages because
there is no any Debian one. ;)

Thanks a lot!



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

Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=es_ES.utf8, LC_CTYPE=es_ES.utf8 (charmap=UTF-8), 
LANGUAGE=es_ES.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: sysvinit (via /sbin/init)

Versions of packages xfce4-goodies depends on:
ii  gnome-shell [notification-daemon]   3.22.3-3
ii  mousepad0.4.0-4
ii  notification-daemon 3.20.0-1+b1
ii  plasma-workspace [notification-daemon]  4:5.8.7-1
ii  ristretto   0.8.2-1
ii  thunar-archive-plugin   0.3.1-4
ii  thunar-media-tags-plugin0.2.1-1+b2
ii  xfburn  0.5.4-1
ii  xfce4-battery-plugin1.1.0-1
ii  xfce4-clipman-plugin2:1.4.1-1
ii  xfce4-cpufreq-plugin1.1.3-1
ii  xfce4-cpugraph-plugin   1.0.5-1+b1
ii  xfce4-datetime-plugin   0.7.0-1
ii  xfce4-dict  0.7.2-1
ii  xfce4-diskperf-plugin   2.5.5-1+b1
ii  xfce4-fsguard-plugin1.0.2-1+b1
ii  xfce4-genmon-plugin 3.4.0-2+b1
ii  xfce4-mailwatch-plugin  1.2.0-2+b2
ii  xfce4-mount-plugin  0.6.7-1+b1
ii  xfce4-netload-plugin1.2.4-2
ii  xfce4-notes-plugin  1.8.1-1
ii  xfce4-notifyd [notification-daemon] 0.3.4-1
ii  xfce4-places-plugin 1.7.0-3
ii  xfce4-screenshooter 1.8.2-2
ii  xfce4-sensors-plugin1.2.6-1+b1
ii  xfce4-smartbookmark-plugin  0.4.6-2
ii  xfce4-systemload-plugin 1.1.2-1+b1
ii  xfce4-taskmanager   1.1.0-1
ii  xfce4-terminal  0.8.4-1
ii  xfce4-timer-plugin  1.6.0-1+b1
ii  xfce4-verve-plugin  1.1.0-1
ii  xfce4-wavelan-plugin0.6.0-1
ii  xfce4-weather-plugin0.8.9-1
ii  xfce4-whiskermenu-plugin1.6.2-1
ii  xfce4-xkb-plugin1:0.7.1-2+b1

Versions of packages xfce4-goodies recommends:
ii  xfce4-power-manager  1.4.4-4

Versions of packages xfce4-goodies suggests:
ii  gigolo  0.4.2-1+aptbuild1
ii  parole  0.8.1-1
pn  xfce4-cellmodem-plugin  
pn  xfce4-hdaps 
ii  xfce4-linelight-plugin  0.1.7-4+b1
ii  xfce4-messenger-plugin  0.1.0-6+b1
pn  xfce4-mpc-plugin
ii  xfce4-radio-plugin  0.5.1-4
pn  xfswitch-plugin 

-- no debconf information

Bug#743179: the order of syntax definitions in nanorc matters

[Benno Schulenberg]

Hello Bernward,


I checked the regexes and could not find any clou, that the regex for awk could
catch shell scripts:


Okay.


If a wrong regex would be the cause of the problem, the effect should be a wrong
syntax highlighting, but not just _no_ highlighting.


Correct.

To figure out what is going wrong, please move your /etc/nanorc and your .nanorc
to a safe place, and then force a reinstall of nano.  This should put a correct
/etc/nanorc back into your filesystem.  Check whether shell scripts are colored
correctly now.  If yes, then again make your one-line .nanorc, that does an 
include
of your self-made awk.nanorc.  Then check again if shell scripts get colored 
okay.
If not, then please show me the exact contents of your .nanorc, your awk.nanorc,
and your /etc/nanorc.

(I have just run 2.2.6, and when I use your one-line .nanorc, shell scripts 
still
get colored fine, so... it's not a fault in 2.2.6 proper.  But... now I see that
your nano has a strange version number: 2.2.6-1+b1.  That version I cannot find
anywhere in Debian.  The only 2.2.6 version is in oldstable, and that is 2.2.6-3
(https://packages.debian.org/source/oldstable/nano).  So...  Did you compile 
nano
yourself?  Or are you on something else than plain Debian?)


In the meantime, I found two things which seem noteworthy, one information and
one rumour:

1) on the nano home page, the recommendation for the current version 2.8 to 
build
a user specific .nanorc still suggests to copy the sample.nanorc to start with,
which is the same as copying /etc/nanorc


It is only the same as copying /etc/nanorc, because distros copy the sample 
rcfile
to /etc/nanorc.  Which is good -- it should be the recommended practice.


[https://www.nano-editor.org/dist/v2.8/faq.html#3.9a]. This means, that puting
only selected commands in .nanorc ist _not_ recommended.


No, one shouldn't read it like that.  That FAQ item was written long ago; I will
change it to say one should read 'man nanorc' and then edit ~/.nanorc and put
there just the few settings that one wants.  I suppose that the recommendation
to copy the sample.nanorc file to ~/.nanorc was made just so that you don't need
to have two terminals open side-by-side but have all the data right there in one
file and you can just throw away what you don't need and uncomment the things
that you want.  But I never did it that way.  I always just put the settings
that I needed into ~/.nanorc, like set boldtext, set nowrap, set smooth, and
set quickblank.


2) On https://github.com/nanorc/nanorc I found an anonymous rumour: „There
appears to be a bug in older versions of nano that causes highlighting to fail
when /etc/nanorc and ~/.nanorc both contain syntax rules. The usual workaround 
is
to remove all syntax and include commands from one file or the other, or to use 
a
newer version of nano.“ But I could not find a reference for this statement nor 
a
version, for which it should be valid.

I suspect that that rumour was caused by your bug report three years ago.  :)

Let's find out where things go wrong by first making your situation as standard
as possible, as described above, and then making small modifications.

Regards,

Benno

Bug#862961: jessie-pu: package libembperl-perl/2.5.0-4+deb8u1

[gregor herrmann]

On Wed, 28 Jun 2017 00:51:33 +0200, Cyril Brulebois wrote:

> > I've prepared an update for libembperl-perl in jessie to fix #810655
> > there as well. The changes are just the targetted fix taken from -5
> > without changes. Full debdiff attached.
> 
> > diff --git a/debian/changelog b/debian/changelog
> > index b59bf9e..e296d69 100644
> > --- a/debian/changelog
> > +++ b/debian/changelog
> > @@ -1,3 +1,11 @@
> > +libembperl-perl (2.5.0-4+deb8u1) UNRELEASED; urgency=medium
> > +
> > +  [ Axel Beckert ]
> > +  * Drop hard a2enmod dependency on mod_perl in zembperl.load. mod_perl is
> > +enabled by default anyways if installed. (Closes: #810655)
> > +
> > + -- gregor herrmann   Fri, 19 May 2017 13:09:03 +0200
> > +
> 
> I haven't matched this to code changes at first glance. For the sake of
> clarity: this relates to the Depends → Recommends update, because code
> was added to “apache2_invoke enmode perl” where needed?

Thanks for asking; this made me look at the changes again, and made
me realize that I made a mistake (I took only one of Axel's commits
between 2.5.0-4 and 2.5.0-5 but there were actually three). Sorry for
that.
 
> (The second sentence makes it look like this /was/ the case already,
> while this seems to /become/ the case with this particular upload
> AFAIUI.)

The problem in #810655, as I understand it, is that d/control has
libapache2-mod-perl2 in Recommends (which is correct as embperl
doesn't require it) but that embperl's
/etc/apache2/mods-available/zembperl.load unconditionally tried to
load mod_perl.
 

Axel has in a later commit removed the changes in libembperl-perl.postinst
again, after verifying that embperl installs without mod_perl, with
mod_perl installed and activated and with mod_perl installed but
disabled.


So the only remaining code change is actually:

#v+
--- a/debian/zembperl.load.in
+++ b/debian/zembperl.load.in
@@ -1,6 +1,6 @@
 # The sucky "zembperl" name is so we load after perl

-# Depends: perl
+# Recommends: perl

 
   LoadModule embperl_module @ARCHLIB@/auto/Embperl/Embperl.so
#v-


I've now tentatively changed d/changelog to say

#v+
  * Change hard dependency on mod_perl in zembperl.load to Recommends.
mod_perl is not required, and is enabled by default anyway if it is
installed.
This change matches the package dependencies and fixes an installation
failure when libapache2-mod-perl2 is not installed.
(Closes: #810655)
#v-


Does this make sense?


I'm attaching the full new debdiff, and I'm looping in Axel for a
sanity check.


Cheers,
gregor


-- 
 .''`.  https://info.comodo.priv.at/ - Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Tom Waits: Sins Of My Father
diff --git a/debian/changelog b/debian/changelog
index b59bf9e..b2e9d48 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,15 @@
+libembperl-perl (2.5.0-4+deb8u1) UNRELEASED; urgency=medium
+
+  [ Axel Beckert ]
+  * Change hard dependency on mod_perl in zembperl.load to Recommends.
+mod_perl is not required, and is enabled by default anyway if it is
+installed.
+This change matches the package dependencies and fixes an installation
+failure when libapache2-mod-perl2 is not installed.
+(Closes: #810655)
+
+ -- gregor herrmann   Fri, 19 May 2017 13:09:03 +0200
+
 libembperl-perl (2.5.0-4) unstable; urgency=low
 
   [ Salvatore Bonaccorso ]
diff --git a/debian/zembperl.load.in b/debian/zembperl.load.in
index ce9542b..91bb120 100644
--- a/debian/zembperl.load.in
+++ b/debian/zembperl.load.in
@@ -1,6 +1,6 @@
 # The sucky "zembperl" name is so we load after perl
 
-# Depends: perl
+# Recommends: perl
 
 
   LoadModule embperl_module @ARCHLIB@/auto/Embperl/Embperl.so


signature.asc
Description: Digital Signature

Bug#810655: Pending fixes for bugs in the libembperl-perl package

[pkg-perl-maintainers]

tag 810655 + pending
thanks

Some bugs in the libembperl-perl package are closed in revision
194fb7ed24f01b9decb27d0cbc766e3a1bb9ba6c in branch '  jessie' by Axel
Beckert

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-perl/packages/libembperl-perl.git/commit/?id=194fb7e

Commit message:

Don't try to enable mod_perl upon libembperl-perl installation

When libapache2-mod-perl2 is being installed, it enables mod_perl by
default. This also is the case if pulled in by libembperl-perl via
Recommends.

So if libapache2-mod-perl2 but not enabled, that's a local
administrator decision which should be honoured (and actually is
honoured by apache2_invoke, so the removed lines were defacto a no-op
anyways).

Closes: #810655 (properly and with minimal changes)

Bug#866242: ITP: node-editor -- Launch the $EDITOR in your program.

[Saravanan P]

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

* Package name: node-editor
  Version : 1.0.0
  Upstream Author : James Halliday  (http://substack.net)
* URL : https://github.com/substack/node-editor
* License : Expat
  Programming Lang: JavaScript
  Description : Launch the $EDITOR in your program

 Launch the $EDITOR (or opts.editor) for file.
 When the editor exits, cb(code, sig) fires.
 .
 This library is a dependency of npm, Node.js package manager.
 .
 Node.js is an event-based server-side JavaScript engine.

Bug#866160: closed by Gianfranco Costamagna <locutusofb...@debian.org> (Re: Bug#866160: RFS: moka-icon-theme/5.3.6-1)

[Gianfranco Costamagna]

Hello

>Quick question.  I can see the moka-icon-theme v5.6.1 source has
>entered the unstable archive - but I don't see the built binary
>
>(all.deb).
>http://cdn-fastly.deb.debian.org/debian/pool/main/m/moka-icon-theme/


some autodecruft removed the binary because of slow builders
https://ftp-master.debian.org/new.html

it is in binNEW queue right now

>Any idea where the binary has gone?  I presume that is the reason why>the 
>package hasnt sync'd to launchpad.net


this is probably due to the network being so slw today

we had some slow dinstalls and probably LP will catch up only tonight

G.

Bug#820354: network-manager: CVE-2016-0764

[Emilio Pozuelo Monfort]

On 17/06/17 16:04, Michael Biebl wrote:
> On Thu, 7 Apr 2016 19:43:36 +0200 Salvatore Bonaccorso
>  wrote:
>> Source: network-manager
>> Version: 0.9.4.0-10
>> Conrol: fixed -1 1.1.91-1
>>
>> Hi,
>>
>> On Wed, Apr 06, 2016 at 11:25:58PM +0200, Michael Biebl wrote:
>>> Hi Moritz,
>>>
>>> Am 06.04.2016 um 22:08 schrieb Moritz Muehlenhoff:
 Hi Michael,
 there's CVE-2016-0764 for network-manager:
 https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=60b7ed3bdc3941a3b7c56824fba4b7291e79041f
  (1.2-beta2)

 It's also fixed in 1.0.12:
 https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/NEWS?h=1.0.12

 This doesn't warrant a DSA, but you can fix it through a jessie
 point update.
>>>
>>> Could you turn this into a bug report please, otherwise I'll most
>>> certainly forget.
>>
>> Forwarding this to the BTS.
> 
> With stretch being released any moment now, this will have to be handled
> as a debian-lts / oldstable upload.
> 
> CCing the debian-lts mailing list, in case they want to make an upload
> for this issue (it's not DSA tracked)

jessie is not handled by the LTS team yet. Besides it's still open, you can do a
jessie-pu upload.

Cheers,
Emilio

Bug#800038: cherry-picked fix from upstream

[dann frazier]

tags 800038 + fixed-upstream
tags 800038 + patch
thanks

This is now fixed upstream.
diff -Nru freeipmi-1.4.11/debian/changelog freeipmi-1.4.11/debian/changelog
--- freeipmi-1.4.11/debian/changelog	2016-09-05 01:55:48.0 -0600
+++ freeipmi-1.4.11/debian/changelog	2017-06-28 11:14:53.0 -0600
@@ -1,3 +1,10 @@
+freeipmi (1.4.11-1.2) UNRELEASED; urgency=medium
+
+  * Use kernel DMI table interface, when available, instead of trolling
+/dev/mem to avoid a crash on ARM.
+
+ -- dann frazier   Wed, 28 Jun 2017 11:14:53 -0600
+
 freeipmi (1.4.11-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru freeipmi-1.4.11/debian/patches/series freeipmi-1.4.11/debian/patches/series
--- freeipmi-1.4.11/debian/patches/series	2016-09-05 01:55:48.0 -0600
+++ freeipmi-1.4.11/debian/patches/series	2017-06-28 11:14:29.0 -0600
@@ -1 +1,2 @@
 deb_bmc-watchdog_noRUN
+Using-DMI-firmware-in-sysfs-if-exists.patch
diff -Nru freeipmi-1.4.11/debian/patches/Using-DMI-firmware-in-sysfs-if-exists.patch freeipmi-1.4.11/debian/patches/Using-DMI-firmware-in-sysfs-if-exists.patch
--- freeipmi-1.4.11/debian/patches/Using-DMI-firmware-in-sysfs-if-exists.patch	1969-12-31 17:00:00.0 -0700
+++ freeipmi-1.4.11/debian/patches/Using-DMI-firmware-in-sysfs-if-exists.patch	2017-06-28 11:14:25.0 -0600
@@ -0,0 +1,102 @@
+From 605065165653e025234ebf135bdeb2e6110070ef Mon Sep 17 00:00:00 2001
+From: Ike Panhc 
+Date: Tue, 27 Jun 2017 16:07:40 +0800
+Subject: [PATCH] Using DMI firmware in sysfs if exists
+
+On arm64 system scanning /dev/mem for SMBIOS tables might fail and
+stopped with SIGBUS. Kernel version > 4.2 provides DMI tables in
+/sys/firmware/dmi/tables and it is much safer for ipmi-locate to
+read. If it exists, reading from it instead of /dev/mem fix
+ipmi-locate crash on several arm64 system.
+
+Unfortunately mmap() does not work on DMI tables so also fallback to
+read if mmap() failed.
+
+Signed-off-by: Ike Panhc 
+---
+ libfreeipmi/locate/ipmi-locate-dmidecode.c | 28 +++-
+ 1 file changed, 23 insertions(+), 5 deletions(-)
+
+diff --git a/libfreeipmi/locate/ipmi-locate-dmidecode.c b/libfreeipmi/locate/ipmi-locate-dmidecode.c
+index 8a89fc025..db1c47387 100644
+--- a/libfreeipmi/locate/ipmi-locate-dmidecode.c
 b/libfreeipmi/locate/ipmi-locate-dmidecode.c
+@@ -115,7 +115,6 @@ struct dmi_header
+   fipmiu16 handle;
+ };
+ 
+-#ifndef HAVE_MMAP
+ static int
+ _myread (ipmi_locate_ctx_t ctx,
+  int fd,
+@@ -155,7 +154,6 @@ _myread (ipmi_locate_ctx_t ctx,
+ 
+   return (0);
+ }
+-#endif
+ 
+ static int
+ _checksum (const fipmiu8 *buf, size_t len)
+@@ -233,14 +231,16 @@ _mem_chunk (ipmi_locate_ctx_t ctx,
+base - mmoffset)) == MAP_FAILED)
+ {
+   LOCATE_ERRNO_TO_LOCATE_ERRNUM (ctx, errno);
+-  goto cleanup;
++  goto try_read;
+ }
+ 
+   memcpy (p, (fipmiu8 *) mmp + mmoffset, len);
+   rv = p;
+   /* ignore potential error, just return result */
+   munmap (mmp, mmoffset + len);
+-#else /* HAVE_MMAP */
++  goto cleanup;
++ try_read:
++#endif /* HAVE_MMAP */
+ 
+   if (lseek (fd, base, SEEK_SET) < 0)
+ {
+@@ -252,7 +252,6 @@ _mem_chunk (ipmi_locate_ctx_t ctx,
+ goto cleanup;
+ 
+   rv = p;
+-#endif /* HAVE_MMAP */
+ 
+  cleanup:
+   /* ignore potential error, cleanup path */
+@@ -457,6 +456,8 @@ ipmi_locate_dmidecode_get_device_info (ipmi_locate_ctx_t ctx,
+   char linebuf[64];
+   fipmiu8 *buf = NULL;
+   int rv = -1;
++  static char const sys_fw_dmi_tables[] = "/sys/firmware/dmi/tables/DMI";
++  struct stat st;
+ 
+   if (!ctx || ctx->magic != IPMI_LOCATE_CTX_MAGIC)
+ {
+@@ -471,6 +472,23 @@ ipmi_locate_dmidecode_get_device_info (ipmi_locate_ctx_t ctx,
+ }
+ 
+   memset (_info, '\0', sizeof (struct ipmi_locate_info));
++
++  /* if DMI firmware exist, use it and do not dig into /dev/mem */
++  if (!(stat (sys_fw_dmi_tables, )))
++{
++  rv = _dmi_table (ctx,
++0,
++st.st_size,
++st.st_size / 4,
++0,
++sys_fw_dmi_tables,
++type,
++_info);
++  if (!(rv))
++memcpy (info, _info, sizeof (struct ipmi_locate_info));
++  return (rv);
++}
++
+   /*
+* Linux up to 2.6.6-rc2: /proc/efi/systab
+* Linux 2.6.6-rc3 and up: /sys/firmware/efi/systab
+-- 
+2.13.2
+

Bug#865483: jessie-pu: package libosinfo/0.2.11-1.1+deb8u1

[Guido Günther]

Hi Cyril,
On Tue, Jun 27, 2017 at 09:24:03PM +0200, Cyril Brulebois wrote:
> Hi Guido,
> 
> Guido Günther  (2017-06-27):
> > One thing that just crossed my mind: should we delay this update for
> > Jessie past the first stretch point release. I would then change the
> > patch to use an URL for stretch from
> > 
> > http://cdimage.debian.org/mirror/cdimage/archive/9.0.0
> > 
> > instead of
> > 
> > http://cdimage.debian.org/mirror/cdimage/release/
> > 
> > so we have a stable URL that doesn't break with every stretch point
> > release asking for further updates? Sorry for not thinking about this
> > earlier.
> 
> It's likely we'll release 8.9 & 9.1 during the same week-end. So maybe
> you could include this change right away? It would only be an annoyance
> for people fetching the updated package “in advance” from the
> jessie-proposed-updates suite? But then, we don't have stretch support
> at all right now, so that's not even a regression.

Great. See new debdiff attached. I've also attached the diff with
patches applied for the relevant part of the debian.xml.in
(url-change.diff). For the sake of completeness: I've also changed
debian/gbp.conf to point to debian/jessie so gbp picks up the right
chroot withou further typing.

Tested on Jessie:

$ osinfo-detect debian-9.0.0-amd64-netinst.iso 
Media is bootable.
Media is an installer for OS 'Debian Stretch'

O.k. to upload to jessie-p-u?
Cheers,
 -- Guido

> 
> > Regarding the tests:
> > 
> > Things are split up in stretch so that tests/ are in libosinfo while the
> > data is in osinfo-db:
> > 
> > 
> > https://gitlab.com/agx1/libosinfo/commit/117029715f90c5c7a2f2a996b21e9fefca6585c8
> > 
> > and I deemed updating libosifo in stretch as well only for the tests
> > overkill (but I ran them there as well).
> 
> (Just to be clear: I was really enjoying seeing tests get added.)
> 
> 
> KiBi.


diff --git a/data/oses/debian.xml.in b/data/oses/debian.xml.in
index 5924850..73bc327 100644
--- a/data/oses/debian.xml.in
+++ b/data/oses/debian.xml.in
@@ -334,7 +334,7 @@
 
 
 
-  http://cdimage.debian.org/cdimage/release/current/i386/iso-cd/debian-9.0.0-i386-netinst.iso
+  http://cdimage.debian.org/mirror/cdimage/archive/9.0.0/i386/iso-cd/debian-9.0.0-i386-netinst.iso
   
 Debian 9.\d.\d i386 (1|n)
   
@@ -342,7 +342,7 @@
   install.386/initrd.gz
 
 
-  http://cdimage.debian.org/cdimage/release/current/amd64/iso-cd/debian-9.0.0-amd64-netinst.iso
+  http://cdimage.debian.org/mirror/cdimage/archive/9.0.0/amd64/iso-cd/debian-9.0.0-amd64-netinst.iso
   
 Debian 9.\d.\d amd64 (1|n)
   
diff --git a/debian/changelog b/debian/changelog
index 45f9af0..10d7772 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+libosinfo (0.2.11-2) jessie; urgency=medium
+
+  * [4b4388e] Add Debian Jessie and Stretch
+  * [335f18d] Adjust gbp.conf for Debian Jessie
+
+ -- Guido Günther   Wed, 28 Jun 2017 19:06:22 +0200
+
 libosinfo (0.2.11-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff --git a/debian/gbp.conf b/debian/gbp.conf
index 4b41283..9103184 100644
--- a/debian/gbp.conf
+++ b/debian/gbp.conf
@@ -1,4 +1,4 @@
 [DEFAULT]
-debian-branch = debian/sid
+debian-branch = debian/jessie
 upstream-tag = v%(version)s
 upstream-branch = upstream/master
diff --git a/debian/patches/Add-Debian-Jessie-and-Stretch.patch b/debian/patches/Add-Debian-Jessie-and-Stretch.patch
new file mode 100644
index 000..fd7e856
--- /dev/null
+++ b/debian/patches/Add-Debian-Jessie-and-Stretch.patch
@@ -0,0 +1,242 @@
+From: =?utf-8?q?Guido_G=C3=BCnther?= 
+Date: Wed, 21 Jun 2017 08:36:07 +0200
+Subject: Add Debian Jessie and Stretch
+
+---
+ data/oses/debian.xml.in| 100 -
+ .../debian/debian8/debian-8.7.1-amd64-CD-1.iso.txt |  29 ++
+ .../debian9/debian-9.0-amd64-netinst.iso.txt   |  29 ++
+ .../debian/debian9/debian-9.0-amd64.iso.txt|  29 ++
+ 4 files changed, 185 insertions(+), 2 deletions(-)
+ create mode 100644 test/isodata/debian/debian8/debian-8.7.1-amd64-CD-1.iso.txt
+ create mode 100644 test/isodata/debian/debian9/debian-9.0-amd64-netinst.iso.txt
+ create mode 100644 test/isodata/debian/debian9/debian-9.0-amd64.iso.txt
+
+diff --git a/data/oses/debian.xml.in b/data/oses/debian.xml.in
+index 61d4d52..73bc327 100644
+--- a/data/oses/debian.xml.in
 b/data/oses/debian.xml.in
+@@ -238,7 +238,7 @@
+ 
+ 
+ 
+-  http://cdimage.debian.org/debian-cd/7.3.0/i386/iso-dvd/debian-7.3.0-i386-DVD-1.iso
++  http://cdimage.debian.org/mirror/cdimage/archive/7.11.0/i386/iso-dvd/debian-7.11.0-i386-DVD-1.iso
+   
+ Debian 7.\d.\d i386 1
+   
+@@ -246,7 +246,7 @@
+   install.386/initrd.gz
+ 
+ 
+-  http://cdimage.debian.org/debian-cd/7.3.0/amd64/iso-dvd/debian-7.3.0-amd64-DVD-1.iso
++  

Bug#865560: Processing of gexiv2_0.10.6-1_amd64.changes

[Gianfranco Costamagna]

yep, removing it

G.




Il Mercoledì 28 Giugno 2017 17:48, Jason Crain  ha scritto:



On Wed, Jun 28, 2017 at 03:15:20PM +, Debian FTP Masters wrote:
> /gexiv2_0.10.6-1_amd64.changes is already present on target host:
> 9-day/libgexiv2-doc_0.10.6-1_all.deb
> Either you already uploaded it, or someone else came first.
> Job gexiv2_0.10.6-1_amd64.changes removed.
> 
> Greetings,
> 
> Your Debian queue daemon (running on host usper.debian.org)
> 

I think the old upload may need to be removed first.

Bug#806331: [xz-devel] Re: xz-utils: make the selected POSIX shell stable accross build environments

[Ximin Luo]

Ximin Luo:
> Lasse Collin:
>> posix-shell.m4 comes from gnulib
>>
>> [..]
>>
>> One can force the POSIX shell to a specific value on the configure
>> command line by passing, for example, "gl_cv_posix_shell=/bin/sh" as an
>> argument. It's not documented in the --help output but it's mentioned
>> in INSTALL section 3.1. That is an alternative to patching to get
>> reproducible builds.
>>
> 
> Hi Lasse,
> 
> Looks like the gnulib guys weren't willing to accept my patch so I'll go the 
> gl_cv_posix_shell route. This is Debian-specific, so xz-utils won't need to 
> make any changes.
> 
> Thanks for your time and your pointers!
> 
> @Debian maintainer, please see the attached patch.
> 

I've uploaded this to DELAYED/14. The debdiff is attached, it's the same patch 
as before just with a proper changelog entry.

X

-- 
GPG: ed25519/56034877E1F87C35
GPG: rsa4096/1318EFAC5FBBDBCE
https://github.com/infinity0/pubkeys.git
diff -Nru xz-utils-5.2.2/debian/changelog xz-utils-5.2.2/debian/changelog
--- xz-utils-5.2.2/debian/changelog 2016-10-08 15:11:19.0 +0200
+++ xz-utils-5.2.2/debian/changelog 2017-06-28 18:39:19.0 +0200
@@ -1,3 +1,11 @@
+xz-utils (5.2.2-1.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Force a constant /bin/sh for installed scripts. This helps the build
+be reproducible; /bin/sh on Debian is always POSIX. (Closes: #806331)
+
+ -- Ximin Luo   Wed, 28 Jun 2017 18:39:19 +0200
+
 xz-utils (5.2.2-1.2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru xz-utils-5.2.2/debian/rules xz-utils-5.2.2/debian/rules
--- xz-utils-5.2.2/debian/rules 2016-10-08 15:01:46.0 +0200
+++ xz-utils-5.2.2/debian/rules 2017-06-28 18:11:21.0 +0200
@@ -66,12 +66,14 @@
 
 debian/normal-build/Makefile debian/normal-build/Doxyfile: $(configure_input)
dh_auto_configure --builddirectory debian/normal-build -- \
+   $(opt_reproduce) \
--enable-threads --disable-static \
$(opt_optimize) $(opt_quiet) \
--disable-xzdec --disable-lzmadec
 
 debian/static-build/Makefile: $(configure_input)
dh_auto_configure --builddirectory debian/static-build -- \
+   $(opt_reproduce) \
--disable-threads --disable-shared \
--enable-liblzma2-compat \
$(opt_optimize) $(opt_quiet) \
@@ -81,6 +83,7 @@
 
 debian/xzdec-build/Makefile: $(configure_input)
dh_auto_configure --builddirectory debian/xzdec-build -- \
+   $(opt_reproduce) \
--disable-shared --disable-nls --disable-encoders \
--enable-small --disable-threads \
--disable-liblzma2-compat \
@@ -97,6 +100,7 @@
 flags_cmd = dpkg-buildflags --export=configure
 opt_optimize = $(shell $(flags_cmd))
 opt_optimize_small = $(shell $(small_flags_env) $(flags_cmd))
+opt_reproduce = gl_cv_posix_shell=/bin/sh
 
 opt_no_act =
 opt_quiet =

Bug#862997: jessie-pu: package libx11-protocol-other-perl/28-1+deb8u1

[gregor herrmann]

On Wed, 28 Jun 2017 01:13:37 +0200, Cyril Brulebois wrote:

> gregor herrmann  (2017-05-19):
> > I've prepared an update for libx11-protocol-other-perl in jessie to
> > fix #848060. The only change is to disable a brittle test via
> > debian/rules in order to avoid test/build failures.
> This looks good to me, feel free to upload (targetting jessie); thanks.

Thanks, uploaded.


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at/ - Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Didier Squiban: Marche des conscrits du Faoutet


signature.asc
Description: Digital Signature

Bug#862986: jessie-pu: package libdata-faker-perl/0.10-1+deb8u1

[gregor herrmann]

On Wed, 28 Jun 2017 01:07:24 +0200, Cyril Brulebois wrote:

> gregor herrmann  (2017-05-19):
> > I've prepared an update for libdata-faker-perl which makes sure that
> > tests are run under the C locale in order to avoid test failures as
> > in #808454.
> This looks good to me, feel free to upload (targetting jessie); thanks.

Thanks! Uploaded.


Cheers,
gregor

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


signature.asc
Description: Digital Signature

Bug#862983: jessie-pu: package libsys-syscall-perl/0.25-2+deb8u1

[gregor herrmann]

On Wed, 28 Jun 2017 01:05:23 +0200, Cyril Brulebois wrote:

> gregor herrmann  (2017-05-19):
> > I've prepared an update for libsys-syscall-perl that adds support for
> > more architectures where the package is silently broken in stable
> > right now. The patches are taken unchanged from testing/sid.
> > Fixed bugs: #824843, #824936, #826136
> This looks good to me, feel free to upload (targetting jessie).

Thank you; uploaded.


Cheers,
gregor

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


signature.asc
Description: Digital Signature

Bug#865732: simple-cdd: should depend (or recommend) mtools?

[Holger Levsen]

On Wed, Jun 28, 2017 at 09:47:18AM -0700, Vagrant Cascadian wrote:
> On 2017-06-24, Holger Levsen wrote:
> > I've just created a profile "scdd" which installs one package, simple-cdd 
> > and
> > copies the configuration used on the medium, so that a freshly installed 
> > system
> > is capable of creating simple-cdd's with the very same configuration.
> I'd be interested in including this in the default/example profiles, if
> it's generalizable!
 
it probably is, it's basically this, which of course is a hack and should be
done more nicely… (it's basically still a PoC.)

some-vm:~/Projects/simple-cdd$ cat profiles/scdd.postinst 
#!/bin/bash

set +e

# configure simple-cdd so it's ready to use
mkdir /home/user/Projects/simple-cdd
mkdir -p /home/user/Projects/simple-cdd/profiles
# a simple "cp -r" is probably more in order here…
for i in sh conf postinst preseed packages xz ; do
cp -r /media/cdrom/simple-cdd/*.$i 
/home/user/Projects/simple-cdd/profiles/
done
mv /home/user/Projects/simple-cdd/profiles/build.sh 
/home/user/Projects/simple-cdd/
chown -R user:user /home/user/Projects/simple-cdd

some-vm:~/Projects/simple-cdd$ cat profiles/scdd.packages 
simple-cdd
mtools
some-vm:~/Projects/simple-cdd$ 

> > This works nicely, with one small issue: I also had to install mtools 
> > manually
> > on the fresh installed system, somehow it doesnt get pulled in by 
> > simple-cdd…
> 
> Hmmm... debian-cd recommends mtools, not sure why it doesn't get
> included. Might be something in tmp/logs/ suggesting why.
> 
> The dependency resolver for simple-cdd is kind of hacky, so it's not
> totally surprising...

I see. I might investigate in a few weeks… ;-) (extremely short on time atm, 
sorry.)

Til then, let's keep this bug report open(?!?), even if only to track the 
feature
described at the top :-)


-- 
cheers,
Holger


signature.asc
Description: Digital signature

Bug#862976: jessie-pu: package libhttp-proxy-perl/0.301-1+deb8u1

[gregor herrmann]

On Wed, 28 Jun 2017 00:59:29 +0200, Cyril Brulebois wrote:

> gregor herrmann  (2017-05-19):
> > I've prepared an update for libhttp-proxy-perl in jessie to fix
> > #788350. The update adds a patch from the recent upstream release
> > (which is in testing/unstable, and we've also used the patch before
> > it was released). Full debdiff attached.
> This looks good to me, feel free to upload (targetting jessie).

Thank you; uploaded.


Cheers,
gregor

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


signature.asc
Description: Digital Signature

Bug#866241: diffoscope: add a --exclude-toplevel-metadata option to help reprotest be less scary

[Ximin Luo]

Package: diffoscope
Version: 83
Severity: wishlist

Dear Maintainer,

Several times people on IRC have asked about reprotest reporting file 
permissions
differences when building files. This can be reproduced trivially:

$ reprotest 'touch x' x
[..]
│ │ │ -Access: (0644/-rw-r--r--)  Uid: ( 1000/infinity0)   Gid: ( 
1000/infinity0)
│ │ │ +Access: (0664/-rw-rw-r--)  Uid: ( 1000/infinity0)   Gid: ( 
1000/infinity0)
[..]
│ │ │ -group::r--
│ │ │ +group::rw-
[..]
exit code 1

This is because diffoscope compares the metadata of its command-line arguments
by default (which is actually a property of the parent directory and not the
file itself). For reproducibility purposes, this is not usually an issue because
one typically does not distribute x plus its current directory metadata, but
only the contents of x.

This can confuse newbies who might not be confident about what reproducibility
means, and assume that "the tool is right".

In order to avoid a diff like this, one has to do something like

$ reprotest 'umask 022; touch x' x
[..]
===
Reproduction successful
===
No differences in x
e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855  x

which is needlessly pointless.

However, sometimes people using diffoscope might indeed want to compare the
metadata of its arguments, e.g. after doing "make install" or similar.

Therefore, we could add a --exclude-toplevel-metadata flag to diffoscope,
which reprotest users could use via --diffoscope-arg, and this could also
be set by default in any relevant "presets".

This would cover both use cases.

X


-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (300, 'unstable'), (200, 'experimental'), (1, 
'experimental-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages diffoscope depends on:
ii  python33.5.3-1
ii  python3-libarchive-c   2.1-3.1
ii  python3-magic  1:5.30-1
ii  python3-pkg-resources  33.1.1-1

Versions of packages diffoscope recommends:
ii  acl  2.2.52-3+b1
ii  apktool  2.2.1+dfsg-2
ii  binutils-multiarch   2.28-5
ii  bzip21.0.6-8.1
ii  caca-utils   0.99.beta19-2+b2
ii  colord   1.3.3-2
ii  default-jdk [java-sdk]   2:1.8-58
ii  default-jdk-headless 2:1.8-58
ii  enjarify 1:1.0.3-3
ii  fontforge-extras 0.3-4
ii  fp-utils 3.0.0+dfsg-11
ii  fp-utils-3.0.0 [fp-utils]3.0.0+dfsg-11
ii  genisoimage  9:1.1.11-3+b2
ii  gettext  0.19.8.1-2
ii  ghc  8.0.1-17+b1
ii  ghostscript  9.20~dfsg-3.2
ii  gnupg2.1.18-6
ii  imagemagick  8:6.9.7.4+dfsg-11
ii  imagemagick-6.q16 [imagemagick]  8:6.9.7.4+dfsg-11
ii  jsbeautifier 1.6.4-6
ii  llvm 1:3.8-36
ii  mono-utils   4.6.2.7+dfsg-1
ii  openjdk-8-jdk [java-sdk] 8u131-b11-2
ii  openssh-client   1:7.4p1-10
ii  pdftk2.02-4+b2
ii  poppler-utils0.48.0-2
ii  python3-argcomplete  1.8.1-1
ii  python3-debian   0.1.30
ii  python3-guestfs  1:1.34.6-2
ii  python3-progressbar  2.3-4
ii  python3-rpm  4.12.0.2+dfsg1-2
ii  python3-tlsh 3.4.4+20151206-1+b2
ii  rpm2cpio 4.12.0.2+dfsg1-2
ii  sng  1.1.0-1+b1
ii  sqlite3  3.16.2-5
ii  squashfs-tools   1:4.3-3+b1
ii  unzip6.0-21
ii  vim-common   2:8.0.0197-4
ii  xxd  2:8.0.0197-4
ii  xz-utils 5.2.2-1.2+b1

Versions of packages diffoscope suggests:
ii  libjs-jquery  3.1.1-2

-- no debconf information

Bug#862964: jessie-pu: package libhtml-microformats-perl/0.105-2+deb8u1

[gregor herrmann]

On Wed, 28 Jun 2017 00:56:22 +0200, Cyril Brulebois wrote:

> > I've prepared an update of libhtml-microformats-perl in stable to fix
> > #783656. The only change is the addition of the missing dependency.
> This looks good to me, feel free to upload (targetting jessie).

Thank you; uploaded.


Cheers,
gregor

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


signature.asc
Description: Digital Signature

Bug#866240: (installation-reports: Install after reboot ends in Kernel panic (Stretch 64) second try)

[Dr. Gideon Fell]

Package: Installer

On 06/28/2017 10:39 AM, Debian Bug Tracking System wrote:

Your message didn't have a Package: line at the very first line of the
mail body (part of the pseudo-header), or didn't have a Package: line
at all. Unfortunatly, this means that your message has been ignored
completely.

Without this information we are unable to categorise or otherwise deal
with your problem report. Please _resubmit_ your report to
sub...@bugs.debian.org and tell us which package the
report is for. For help, check out
http://www.debian.org/Bugs/Reporting.

Your message was dated Wed, 28 Jun 2017 10:34:02 -0400 and had
message-id 
and subject installation-reports: Install after reboot ends in Kernel panic 
(Stretch 64) second try.
The complete text of it is attached to this message.

If you need any assistance or explanation please contact
ow...@bugs.debian.org and include the the attached
message.

If you didn't send the attached message (spam was sent forging your
from address), we apologize; please disregard this message.




Subject: installation-reports: Install after reboot ends in Kernel panic 
(Stretch 64)
Package: installation-reports
Severity: important

Dear Maintainer,

SOMETIMES I can do a recovery mode, but even this does not usually work. THe 
computer, with !TB & 2TB hard disks, can boot wiht either Jessie or Wheeezy of 
Jessie with latest kernels. The Debial Live 9.0.1 also gives a kernel panic
*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- Package-specific info:

Boot method: CD
Image version: 
https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-9.0.0-amd64-netinst.iso
Date: 

Machine: ASUS P8Z68-VLX 32 GB RAM, Intel i5
Partitions: 
  This is for the working Jessie (where I'm writing this)
/dev/sda18 ext4  58118364 10439540  44703492  19% /
udev   devtmpfs 102400 10240   0% /dev
tmpfs  tmpfs  6596816 9608   6587208   1% /run
/dev/sda21 ext4  57541628  6118856  48476776  12% /usr
tmpfs  tmpfs 16492040  296  16491744   1% /dev/shm
tmpfs  tmpfs 51204  5116   1% /run/lock
tmpfs  tmpfs 164920400  16492040   0% /sys/fs/cgroup
/dev/sda17 ext437752634417319097  10% /boot
/dev/sda19 ext4  57541628  6530264  48065368  12% /home
/dev/sda20 ext4  57541628  3983400  50612232   8% /opt
/dev/sda15 ext4  45219888  6863536  36036224  16% /home/ron/.thunderbird
/dev/sda13 ext4  32119712 10794264  19670824  36% /home/ron/$
/dev/sda14 ext4  32122784  3356472  27111528  12% /home/ron/.mozilla
tmpfs  tmpfs  32984088   3298400   1% /run/user/117
tmpfs  tmpfs  3298408   16   3298392   1% /run/user/1000

For Stretch sda5 and sdb5 are swap
sda7 is boot
sda10 is home
sda9  is /
sda11 is /usr
sda12 is /opt


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
E kernel panics on rebbot after install

Initial boot:   [X]
Detect network card:[ ]
Configure network:  [ ]
Detect CD:  [ ]
Load installer modules: [ ]
Clock/timezone setup:   [ ]
User/password setup:[ ]
Detect hard drives: [ ]
Partition hard drives:  [ ]
Install base system:[ ]
Install tasks:  [ ]
Install boot loader:[ ]
Overall install:[X]

Comments/Problems:


Plain install, with backports and SSH enabled,
GNOME desktop, with either Kernel installed from the 2 choices given


-- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="8 (jessie) - installer build 20150422"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux Jessie 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt9-2 (2015-04-13) 
x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 2nd Generation Core 
Processor Family DRAM Controller [8086:0100] (rev 09)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:844d]
lspci -knn: Kernel driver in use: snb_uncore
lspci -knn: 00:01.0 PCI bridge [0604]: Intel 

Bug#862960: jessie-pu: package libcgi-application-plugin-anytemplate-perl/0.18-1+deb8u1

[gregor herrmann]

On Wed, 28 Jun 2017 00:46:01 +0200, Cyril Brulebois wrote:

> > I've prepared an update for libcgi-application-plugin-anytemplate-perl
> > in stable to fix #788008. Complete debdiff attached.
> This looks good to me, but please remember to target jessie.
> Feel free to upload, thanks.

Thank you! Uploaded.


Cheers,
gregor

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


signature.asc
Description: Digital Signature

Bug#865732: simple-cdd: should depend (or recommend) mtools?

[Vagrant Cascadian]

On 2017-06-24, Holger Levsen wrote:
> I've just created a profile "scdd" which installs one package, simple-cdd and
> copies the configuration used on the medium, so that a freshly installed 
> system
> is capable of creating simple-cdd's with the very same configuration.

I'd be interested in including this in the default/example profiles, if
it's generalizable!


> This works nicely, with one small issue: I also had to install mtools manually
> on the fresh installed system, somehow it doesnt get pulled in by simple-cdd…

Hmmm... debian-cd recommends mtools, not sure why it doesn't get
included. Might be something in tmp/logs/ suggesting why.

The dependency resolver for simple-cdd is kind of hacky, so it's not
totally surprising...


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#866194: patch: Bug#866194 service fails to start when installing etcd.

[Harish Sriram]

Hi,The following patch solves the issue.Index: etcd-3.1.8+dfsg/etcdmain/etcd.go===--- etcd-3.1.8+dfsg.orig/etcdmain/etcd.go+++ etcd-3.1.8+dfsg/etcdmain/etcd.go@@ -399,7 +399,7 @@ func setupLogging(cfg *config) {
 func checkSupportArch() {        // TODO qualify arm64-       if runtime.GOARCH == "amd64" {+       if runtime.GOARCH == "amd64" || runtime.GOARCH == "ppc64le" {                return        }        if env, ok := os.LookupEnv("ETCD_UNSUPPORTED_ARCH"); ok && env == runtime.GOARCH { Patch and debdiff is attached here. Thanks.Harish Sriram



debdiff_etcd.debdiff
Description: Binary data


fix-service-ppc64le.patch
Description: Binary data

Bug#825643: dash: please make the build reproducible

[Ximin Luo]

Package: src:dash
Followup-For: Bug #825643

Hi, I've uploaded this to DELAYED/14.

The patch is attached, it's just a combined version of what the previous two
bug reporters submitted, plus a changelog.

X

-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (300, 'unstable'), (200, 'experimental'), (1, 
'experimental-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -u dash-0.5.8/debian/changelog dash-0.5.8/debian/changelog
--- dash-0.5.8/debian/changelog
+++ dash-0.5.8/debian/changelog
@@ -1,3 +1,16 @@
+dash (0.5.8-2.5) unstable; urgency=low
+
+  * Non-maintainer upload.
+
+  [ Reiner Herrmann ]
+  * Improve build reproducibility: set LC_ALL instead of LC_COLLATE to C.
+
+  [ HW42 ]
+  * Improve build reproducibility: avoid exec call which embeds different paths
+between different system shells. (Closes: #825643)
+
+ -- Ximin Luo   Wed, 28 Jun 2017 18:26:52 +0200
+
 dash (0.5.8-2.4) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -u dash-0.5.8/debian/rules dash-0.5.8/debian/rules
--- dash-0.5.8/debian/rules
+++ dash-0.5.8/debian/rules
@@ -46,7 +46,7 @@
touch configure
(cd build-tmp && CC='$(CC)' \
  CFLAGS='$(CFLAGS)' CPPFLAGS='$(CPPFLAGS)' LDFLAGS='$(LDFLAGS)' \
- exec ../configure --enable-fnmatch --disable-lineno \
+ ../configure --enable-fnmatch --disable-lineno \
--host='$(DEB_HOST_GNU_TYPE)')
touch configure-stamp
 
only in patch2:
unchanged:
--- dash-0.5.8.orig/src/mkbuiltins
+++ dash-0.5.8/src/mkbuiltins
@@ -78,7 +78,7 @@
if ($i ~ /^-/)
line = $(++i) "\t" line
print line
-   }}' $temp | LC_COLLATE=C sort -k 1,1 | tee $temp2 | awk '{
+   }}' $temp | LC_ALL=C sort -k 1,1 | tee $temp2 | awk '{
opt = ""
if (NF > 2) {
opt = substr($2, 2)
@@ -97,7 +97,7 @@
  */
 
 !
-sed 's/-[a-z]*//' $temp2 | nl -b a -v 0 | LC_COLLATE=C sort -u -k 3,3 |
+sed 's/-[a-z]*//' $temp2 | nl -b a -v 0 | LC_ALL=C sort -u -k 3,3 |
 tr abcdefghijklmnopqrstuvwxyz ABCDEFGHIJKLMNOPQRSTUVWXYZ |
awk '{  printf "#define %s (builtincmd + %d)\n", $3, $1}'
 printf '\n#define NUMBUILTINS %d\n' $(wc -l < $temp2)

Bug#758234: debian-policy: allow packages to depend on packages of lower priority

[Russ Allbery]

Andreas Henriksson  writes:

> Can't help but wonder why not just remove the "extra" (and mentioning it
> as deprecated in upgrade notes) rather than explicitly documenting it as
> deprecated. I guess keeping it around is useful to avoid people
> mass-bug-filing RC-bugs for all current extra packages.

I'd like to keep the documentation of extra because, for some time to
come, there will be a lot of packages in the wild that will have that
priority in their control files (even if they've been overridden by
ftp-master in the archive metadata).  We therefore need to document that
the priority still exists.

Hm, it occurs to me that this wording should probably explicitly say that
the extra priority should be treated the same as optional if it appears
anywhere (although the archive-wide override change will mostly take care
of that).

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

Bug#866188: snappy 1.1.4 upstream tarball broken on armhf

[Steve Langasek]

On Wed, Jun 28, 2017 at 08:37:50AM +0200, László Böszörményi (GCS) wrote:
> On Wed, Jun 28, 2017 at 6:23 AM, Steve Langasek
>  wrote:
> > The snappy 1.1.4 release tarball as distributed by upstream does not match
> > its git tag; it contains an additional patch of unclear origin which is
> > broken on armhf (as confirmed on harris.d.o).
>  Ouch! May you know any public QA tool that may be capable of Git tag
> and tarball equality check? Say, an uscan extension?

I don't, sorry.

> > Attached is a patch, which I've applied in Ubuntu, to address both of these
> > issues.  I have also written to upstream about the issue of the wrong
> > tarball.
>  Thanks, please ping me if you get any answer. I may think they have
> an open source release and an internal version of Snappy and that file
> leaked accidentally.

I did get a reply; the plan is to release 1.1.5 in the next few weeks, at
which point the problem is historical.

> > It might be more appropriate to address the missing 'make check' issue by
> > instead migrating debian/rules to pure dh(1), but I would leave that to you
> > as maintainer to decide.
>  For the moment I'll stick to the current, old rules format - I plan
> to use the short debhelper style for the next release.
> 
> Cheers,
> Laszlo/GCS

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature

Bug#866238: debmirror: failed to remove stale InRelease file for Stretch

[Martin Dorey]

Package: debmirror
Version: 1:2.25
Severity: normal

Dear Colin and co,

Before manual intervention to work around this issue, our two Debian mirrors
had files debian/dists/stretch/InRelease, starting like this:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Origin: Debian
Label: Debian
Suite: testing
Codename: stretch
Changelogs: 
http://metadata.ftp-master.debian.org/changelogs/@CHANGEPATH@_changelog
Date: Sat, 17 Jun 2017 02:40:32 UTC
Valid-Until: Sat, 24 Jun 2017 02:40:32 UTC
Acquire-By-Hash: yes
Architectures: amd64 arm64 armel armhf i386 mips mips64el mipsel ppc64el s390x
Components: main contrib non-free
Description: Debian x.y Testing distribution - Not Released
MD5Sum:
 f9bbab6d94f45e56c672017d8720a24c  1181459 contrib/Contents-amd64

Everything was working last week.
This week - so after the Valid-Until date expired - a Stretch installation was 
reported
as failing with:

[!!] Configure the package manager

The installer failed to access the mirror. This may be a problem with your 
network, or with the mirror. You can choose to retry the download, select a 
different mirror, or ignore the problem and continue without all the packages 
from this mirror.

Downloading a file failed:

Retry
Change mirror
Ignore

A packet capture on our mirror showed the following transaction:

No. Abs. Time  TCP #  SourceDestination 
  Protocol Info 
  4 16:52:56.1977970  172.16.222.36 10.72.41.18 
  HTTP GET /debian/dists/stretch/InRelease HTTP/1.1 
  6 16:52:56.1993880  10.72.41.18   172.16.222.36   
  HTTP HTTP/1.1 416 Requested Range Not Satisfiable  (text/html)
  8 16:52:56.2000190  172.16.222.36 10.72.41.18 
  HTTP GET /debian/dists/stretch/InRelease HTTP/1.1 
 60 16:52:56.2039810  10.72.41.18   172.16.222.36   
  HTTP HTTP/1.1 200 OK 

An apt-get update, on a different, existing Stretch installation, failed with:

E: Release file for http://debian-mirror/debian/dists/stretch/InRelease is 
expired (invalid since 3d 15h 0min 58s). Updates for this repository will not 
be applied.

Investigation upstream from there showed that the file had disappeared.
We renamed it aside locally.
Everything started working.
It would have been nice if debmirror had removed the obsoleted and now 
seemingly harmful file.
Perhaps that would be hard.
Manual recovery was easy, once we had a diagnosis
So I post this more in the hope of helping others with the same symptom.
Our-ref: D130753


-- System Information:
Debian Release: 7.3
  APT prefers oldstable-updates
  APT policy: (990, 'oldstable-updates'), (990, 'oldstable'), (500, 
'oldoldstable'), (500, 'stable'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages debmirror depends on:
ii  bzip2   1.0.6-4
pn  libdigest-md5-perl  
ii  liblockfile-simple-perl 0.208-1
ii  libnet-inet6glue-perl   0.5-1
ii  libwww-perl 6.04-1
ii  perl [libdigest-sha-perl]   5.14.2-21+deb7u2
ii  perl-modules [libnet-perl]  5.14.2-21+deb7u2
ii  rsync   3.0.9-4

Versions of packages debmirror recommends:
ii  ed 1.6-2
ii  gpgv   1.4.12-7+deb7u3
ii  patch  2.6.1-3

Versions of packages debmirror suggests:
ii  gnupg  1.4.12-7+deb7u3

-- debconf-show failed

Bug#866239: error: destination /var/log/exim4/mainlog.1.gz already exists

[積丹尼 Dan Jacobson]

Package: logrotate
Version: 3.11.0-0.1
Severity: minor
File: /usr/sbin/logrotate

> "A" == Anacron   writes:
A> /etc/cron.daily/logrotate:
A> error: destination /var/log/exim4/mainlog.1.gz already exists, renaming to 
/var/log/exim4/mainlog.1.gz-2017062900.backup

Bug#866029: with the reproducer

[Nicolas Boulenguez]

Package: gnat-7
Followup-For: Bug #866029
Control: tags -1 + pending

Now with the attachment.
A patch is in the VCS.
#!/bin/sh
set -C -e -f -u

# On a normal installation.
gnatmake=gnatmake

# Alongside a fresh gcc build tree.
# gcctree=..
# target_noncanonical=arm-linux-gnueabi
# exedir=$gcctree/build/gcc
# rtsdir=$gcctree/build/$target_noncanonical/libada
# vsndir=$gcctree/build/$target_noncanonical/libgnatvsn
# export LD_LIBRARY_PATH=$rtsdir/adalib:$vsndir
# echo "LD_LIBRARY_PATH='$LD_LIBRARY_PATH'"
# gnatmake="$exedir/gnatmake --RTS=$rtsdir --GCC=$exedir/xgcc"

rm -f p.ads
echo 'package P is end P;' > p.ads
# Avoid mtime sooner than the one for system.ads.
mtime=$((1000*365*24*60*60))
touch --date=@$mtime p.ads

to_gnat () {
date --utc --date=@$1 +%Y%m%d%H%M%S
}
check () {
rm -f p.ali p.o
$gnatmake -q -c p.ads
expected=`to_gnat $1`
found=`sed -n '/^D p\.ads\t\+\([0-9]\{14\}\) .*/{s//\1/;p;q}' p.ali`
if test "$found" != "$expected"; then
echo "Fail: wrong time stamp in p.ali."
echo "   SOURCE_DATE_EPOCH:   '${SOURCE_DATE_EPOCH:-}'"
echo "   Source file mtime:'`to_gnat $mtime`' ($mtime)"
echo "   Expected in ALI  :'$expected' ($1)"
echo "   Found in ALI :'$found'"
fi
if test "`$gnatmake -c p.ads -eS`" != "gnatmake: objects up to date."; then
echo "Fail: p.ads should not require recompilation."
echo "   SOURCE_DATE_EPOCH:   '${SOURCE_DATE_EPOCH:-}'"
echo "   Source file mtime:'`to_gnat $mtime`' ($mtime)"
echo "   p.ali:'`cat p.ali`'"
echo "   gnatmake -v  :'`$gnatmake -c p.ads -eS -v`'"
fi
}
# SOURCE_DATE_EPOCH is not defined
unset SOURCE_DATE_EPOCH
check "$mtime"
# SOURCE_DATE_EPOCH is invalid or more recent than mtime.
for d in "" a " 1" -0 -1 $(($mtime+10)) 0$(($mtime+10)); do
export "SOURCE_DATE_EPOCH=$d"
check "$mtime"
done
# SOURCE_DATE_EPOCH is valid and older than mtime.
for d in $(($mtime-10)) 0$(($mtime-10)); do
export "SOURCE_DATE_EPOCH=$d"
check "$d"
done
echo "Test finished."

Bug#774449: sensible-utils: please make sensible-utils build reproducibly

[Ximin Luo]

Ximin Luo:
> Hi, here is an updated patch - it gets rid of filesystem and umask 
> differences, which started cropping up. I think previously I was testing with 
> an older version of reprotest, which didn't properly test these differences.
> 
> I also took the chance to refactor the rules file slightly, for readability.
> 

Hi, I have updated the patch and uploaded this to DELAYED/14.

The patch is attached, it's the same one as before just with a "more official" 
changelog.

X

-- 
GPG: ed25519/56034877E1F87C35
GPG: rsa4096/1318EFAC5FBBDBCE
https://github.com/infinity0/pubkeys.git
diff -Nru sensible-utils-0.0.9/debian/changelog 
sensible-utils-0.0.9+nmu1/debian/changelog
--- sensible-utils-0.0.9/debian/changelog   2013-06-06 14:19:53.0 
+0200
+++ sensible-utils-0.0.9+nmu1/debian/changelog  2017-06-28 18:17:02.0 
+0200
@@ -1,3 +1,20 @@
+sensible-utils (0.0.9+nmu1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Jérémy Bobbio ]
+  * Make package build reproducibly:
+- Stop recording current time when creating gzip files.
+- Fix mtimes before creating binary packages.
+
+  [ Ximin Luo ]
+  * Make package build reproducible, pt 2:
+- Sort file list, to avoid filesystem differences.
+- Explicitly install every language man dir, to avoid umask differences.
+- Slightly refactoring for readability.
+
+ -- Ximin Luo   Wed, 28 Jun 2017 18:17:02 +0200
+
 sensible-utils (0.0.9) unstable; urgency=low
 
   * Fix bashism in select-editor
diff -Nru sensible-utils-0.0.9/debian/rules 
sensible-utils-0.0.9+nmu1/debian/rules
--- sensible-utils-0.0.9/debian/rules   2012-05-14 09:23:19.0 +0200
+++ sensible-utils-0.0.9+nmu1/debian/rules  2017-06-28 18:11:41.0 
+0200
@@ -9,6 +9,11 @@
 INSTALL_SCRIPT  = $(INSTALL) -p-o root -g root  -m  755
 INSTALL_DIR = $(INSTALL) -p -d -o root -g root  -m  755
 
+MAN_LANGS = de es fr it ja pl
+MAN_DIRS = $(MAN_LANGS:%=debian/sensible-utils/usr/share/man/%/man1)
+
+BUILD_DATE := $(shell dpkg-parsechangelog | sed -n -e 's/^Date: //p')
+
 DEB_BUILD_ARCH_OS ?= $(shell dpkg-architecture -qDEB_BUILD_ARCH_OS)
 DEB_BUILD_GNU_TYPE = $(shell dpkg-architecture -qDEB_BUILD_GNU_TYPE)
 DEB_HOST_GNU_TYPE = $(shell dpkg-architecture -qDEB_HOST_GNU_TYPE)
@@ -52,41 +57,30 @@
$(INSTALL_DIR) debian/sensible-utils/DEBIAN \
   debian/sensible-utils/usr/bin \
   debian/sensible-utils/usr/share/man/man1 \
+  $(MAN_DIRS) \
   debian/sensible-utils/usr/lib/mime/packages \
   debian/sensible-utils/usr/share/doc/$(package)
$(MAKE) install DESTDIR=$(CURDIR)/debian/sensible-utils 
INSTALL_PROGRAM="$(INSTALL_PROGRAM)"
 
-   ln -s sensible-editor.1.gz 
debian/sensible-utils/usr/share/man/man1/sensible-pager.1.gz
-   ln -s sensible-editor.1.gz 
debian/sensible-utils/usr/share/man/man1/sensible-browser.1.gz
-   ln -s sensible-editor.1.gz 
debian/sensible-utils/usr/share/man/fr/man1/sensible-pager.1.gz
-   ln -s sensible-editor.1.gz 
debian/sensible-utils/usr/share/man/fr/man1/sensible-browser.1.gz
-   ln -s sensible-editor.1.gz 
debian/sensible-utils/usr/share/man/pl/man1/sensible-pager.1.gz
-   ln -s sensible-editor.1.gz 
debian/sensible-utils/usr/share/man/pl/man1/sensible-browser.1.gz
-   ln -s sensible-editor.1.gz 
debian/sensible-utils/usr/share/man/es/man1/sensible-pager.1.gz
-   ln -s sensible-editor.1.gz 
debian/sensible-utils/usr/share/man/es/man1/sensible-browser.1.gz
-   ln -s sensible-editor.1.gz 
debian/sensible-utils/usr/share/man/de/man1/sensible-pager.1.gz
-   ln -s sensible-editor.1.gz 
debian/sensible-utils/usr/share/man/de/man1/sensible-browser.1.gz
-   ln -s sensible-editor.1.gz 
debian/sensible-utils/usr/share/man/ja/man1/sensible-pager.1.gz
-   ln -s sensible-editor.1.gz 
debian/sensible-utils/usr/share/man/ja/man1/sensible-browser.1.gz
-   ln -s sensible-editor.1.gz 
debian/sensible-utils/usr/share/man/it/man1/sensible-pager.1.gz
-   ln -s sensible-editor.1.gz 
debian/sensible-utils/usr/share/man/it/man1/sensible-browser.1.gz
+   set -e; for i in "" $(MAN_LANGS); do \
+   ln -s sensible-editor.1.gz 
debian/sensible-utils/usr/share/man/$$i/man1/sensible-pager.1.gz; \
+   ln -s sensible-editor.1.gz 
debian/sensible-utils/usr/share/man/$$i/man1/sensible-browser.1.gz; \
+   done
$(INSTALL_FILE) debian/changelog 
debian/sensible-utils/usr/share/doc/$(package)
find debian/sensible-utils/usr/share/man/man1 \
-debian/sensible-utils/usr/share/man/es/man1 \
-debian/sensible-utils/usr/share/man/fr/man1 \
-debian/sensible-utils/usr/share/man/pl/man1 \
-debian/sensible-utils/usr/share/man/de/man1 \
-debian/sensible-utils/usr/share/man/ja/man1 \
-debian/sensible-utils/usr/share/man/it/man1 \
- 

Bug#866223: devscripts: Add support for codenames to dch

[Mattia Rizzolo]

Control: forcemerge 789587 -1

On Wed, Jun 28, 2017 at 03:42:14PM +0200, Yves-Alexis Perez wrote:
> the stable release team ack'ed me a package upload to oldstable, and
> requested that I target the upload to 'jessie'. Unfortunately, it seems
> that debchangelog doesn't know about codenames:
> 
> Could it be added at one point?

Did in git a few days ago, and already reported years ago.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#865768: [Bug 784291] Drop down list of tabs missing

[積丹尼 Dan Jacobson]

> "e" == epiphany  <(GNOME Bugzilla) > writes:
e> Michael Catanzaro changed bug 784291

e>  Resolution  ---   OBSOLETE

e> Comment # 1 on bug 784291 from Michael Catanzaro
e> (In reply to Dan Jacobson from comment #0)
>> Where is the drop down list of tabs?

e> I added this in 3.24, so you would have to manually build or upgrade Epiphany
e> beyond what is provided by Debian to get this. Sorry.

Bug#866236: lxqt-core should recommend lxqt-qtplugin

[Alf Gaida]

Package: lxqt-core
Version: lxqt-core should recommend lxqt-qtplugin
Severity: normal
Tags: newcomer

lxqt-qtplugin is needed to pick up the settings from the session.
It should be at least recommend.


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

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

Bug#866234: lxqt-config should recommend lxqt-qtplugin

[Alf Gaida]

Package: lxqt-config
Version: 0.11.2~19-g66a1b23-1
Severity: normal
Tags: newcomer

lxqt-qtplugin is needed to pick up the settings from the session.
It should be at least recommend.


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

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

Versions of packages lxqt-config depends on:
ii  libc6 2.24-12
ii  libkf5screen-bin  4:5.8.6-2
ii  libkf5screen7 4:5.8.6-2
ii  liblxqt0  0.11.2~13-g05e4153
ii  libqt5core5a  5.7.1+dfsg-3+b1
ii  libqt5gui55.7.1+dfsg-3+b1
ii  libqt5svg55.7.1~20161021-2+b2
ii  libqt5widgets55.7.1+dfsg-3+b1
ii  libqt5x11extras5  5.7.1~20161021-2
ii  libqt5xdg22.0.1~54-g075f9f4-1
ii  libqt5xml55.7.1+dfsg-3+b1
ii  libstdc++67.1.0-7
ii  libx11-6  2:1.6.4-3
ii  libxcb-randr0 1.12-1
ii  libxcb1   1.12-1
ii  libxcursor1   1:1.1.14-1+b4
ii  libxfixes31:5.0.3-1
ii  zlib1g1:1.2.8.dfsg-5

Versions of packages lxqt-config recommends:
ii  galternatives 0.13.6
ii  lxqt-config-l10n  0.11.3~31-g70dd9ff4~1

lxqt-config suggests no packages.

-- no debconf information

Bug#866235: lxqt-globalkeys should recommend lxqt-qtplugin

[Alf Gaida]

Package: lxqt-globalkeys
Version: 0.11.2~36-g9e64d65-1
Severity: normal
Tags: newcomer

lxqt-qtplugin is needed to pick up the settings from the session.
It should be at least recommend.


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

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

Versions of packages lxqt-globalkeys depends on:
ii  libc6   2.24-12
ii  libgcc1 1:7.1.0-7
ii  liblxqt00.11.2~13-g05e4153
ii  libqt5core5a5.7.1+dfsg-3+b1
ii  libqt5dbus5 5.7.1+dfsg-3+b1
ii  libqt5gui5  5.7.1+dfsg-3+b1
ii  libqt5widgets5  5.7.1+dfsg-3+b1
ii  libstdc++6  7.1.0-7
ii  libx11-62:1.6.4-3

Versions of packages lxqt-globalkeys recommends:
ii  lxqt-globalkeys-l10n  0.11.3~31-g70dd9ff4~1

lxqt-globalkeys suggests no packages.

-- no debconf information

Bug#866233: lxqt-admin should recommend lxqt-qtplugin

[Alf Gaida]

Package: lxqt-admin
Version: 0.11.2~4-gf7c0daa-1
Severity: normal
Tags: newcomer

lxqt-admin is needed to pick up the settings from the session.
It should be at least recommend.


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

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

Versions of packages lxqt-admin depends on:
ii  libc6   2.24-12
ii  liblxqt00.11.2~13-g05e4153
ii  libqt5core5a5.7.1+dfsg-3+b1
ii  libqt5dbus5 5.7.1+dfsg-3+b1
ii  libqt5gui5  5.7.1+dfsg-3+b1
ii  libqt5widgets5  5.7.1+dfsg-3+b1
ii  libstdc++6  7.1.0-7

Versions of packages lxqt-admin recommends:
ii  lxqt-admin-l10n  0.11.3~31-g70dd9ff4~1

lxqt-admin suggests no packages.

-- no debconf information

Bug#865560: Processing of gexiv2_0.10.6-1_amd64.changes

[Jason Crain]

On Wed, Jun 28, 2017 at 03:15:20PM +, Debian FTP Masters wrote:
> /gexiv2_0.10.6-1_amd64.changes is already present on target host:
> 9-day/libgexiv2-doc_0.10.6-1_all.deb
> Either you already uploaded it, or someone else came first.
> Job gexiv2_0.10.6-1_amd64.changes removed.
> 
> Greetings,
> 
>   Your Debian queue daemon (running on host usper.debian.org)
> 

I think the old upload may need to be removed first.

Bug#772154: closed by Mathieu Parent <math.par...@gmail.com> (Re: Bug#772154: process_usershare_file: stat of/var/lib/samba/usershares/netlogo failed. No such file or directory)

[Marco Gaiarin]

> > I missing the first time :  Can't find include file /etc/samba/smb.conf.
> > whats loading, uh.. whats not loading there.

Sorry, forgot to specify: in smb.conf i've a:

include = /etc/samba/smb.conf.%m

that i use to enable debugging for specific host: eg, for 'testparm' %m
is '', and the file tipically does not exist at all.


> > But if this Marco, is the Marco Gaiarin with GPG : 240A3D66  ;-)  then i say
> > close.  i know its you Marco :-p
> > Marco hase moved to debian stretch.  ;-)

I confirm. Bug closed, or better, ignored. ;-)

Bug#866232: lxqt-about should recommend lxqt-qtplugin

[Alf Gaida]

Package: lxqt-about
Version: 0.11.2~3-gcf5529a-1
Severity: normal
Tags: newcomer

lxqt-qtplugin is needed to pick up the settings from the session.
It should be at least recommend.

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

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

Versions of packages lxqt-about depends on:
ii  libc6   2.24-12
ii  liblxqt00.11.2~13-g05e4153
ii  libqt5core5a5.7.1+dfsg-3+b1
ii  libqt5gui5  5.7.1+dfsg-3+b1
ii  libqt5widgets5  5.7.1+dfsg-3+b1
ii  libqt5xdg2  2.0.1~54-g075f9f4-1
ii  libstdc++6  7.1.0-7

Versions of packages lxqt-about recommends:
ii  lxqt-about-l10n  0.11.3~31-g70dd9ff4~1

lxqt-about suggests no packages.

-- no debconf information

Bug#758234: debian-policy: allow packages to depend on packages of lower priority

[Joerg Jaspert]

On 14717 March 1977, Andreas Henriksson wrote:
> Can't help but wonder why not just remove the "extra" (and mentioning it
> as deprecated in upgrade notes) rather than explicitly documenting it as
> deprecated. I guess keeping it around is useful to avoid people
> mass-bug-filing RC-bugs for all current extra packages.

As soon as this is more than just a discussion but gets reality, we will
ensure there *IS* no more extra package with a mass override change...


-- 
bye, Joerg

Bug#866114: texlive-fonts-extra: Icon errors when installed alongside fonts-font-awesome

[Connor Glosser]

Removing texlive-full fixes the problem. I will try to identify the
specific dependency that causes the issue when I get home tonight.

On Wed, Jun 28, 2017 at 10:26 AM, Norbert Preining 
wrote:

> Hi Connor,
>
> > to specifically remove the fonts-extra problem doesn't fix things which
> > seems to indicate the problem is with another part of texlive-full. Do
> you
>
> No, probably not texlive-full, but with some fonts being installed.
>
> > know of anything else I can check to iron out what might be causing the
> > problem? Running
> >
> > $ fc-list | grep -i awesome
> >
> > gives me the same output as you.
>
> And what about uninstalling all of texlive-full, and also all depending
> packages, and see what happens then?
>
> I have no idea, but TeX Live does not interfer in this area, it adds
> *some* fonts to the fontconfig path, but not all of it, and awesome
> is not included.
>
> All the best
>
> Norbert
>
> --
> PREINING Norbert   http://www.preining.info
> Accelia Inc. +JAIST +TeX Live +Debian Developer
> GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
>

Bug#851633: anacron: run anacron hourly

[Marc Haber]

On Mon, Jan 16, 2017 at 09:49:38PM -0600, Nathan Schulte wrote:
> Currently, Anacron is setup to run once daily.  While this configuration works
> fine, it ends up only supporting longer-duration power-cycles; that is, cycles
> greater than a day.  This is probably good for some server configurations, but
> this is not good for desktop and mobile (laptop) systems that are powered off
> daily or even more periodically.
> 
> In these cases, running Anacron hourly allows the daily scripts to be serviced
> by Anacron as a user expects.  I believe this will resolve these two bug
> reports:
> 
>   1) #619648  cron.daily doesn't execute scheduled scripts
>   2) #672061  [anacron] Daily cronjobs in crontabs of users aren't ran by
>   anacron.

This change will change the time the daily, weekly and monthly cron jobs
run to "first anacron time after midnight", which is way too early in
the day. I surely am not the only person who is frequently still
working at midnight, and having cron.daily run while I'm actively
working is something I don't want to have.

If this is implemented[1], care should be taken that the "old" cron
blocks are not affected by the change.

Greetings
Marc


[1] incidentally, an hourly anacron run is in unstable's anacron since
early June 2017, and the package got accepted for the stretch release a
week later, so we actually have this behavior in a stable release, which
makes me Not Amused.

-- 
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Bug#866231: clang: Missing /usr/lib/ccache/ symlink

[Christian Marillat]

Package: clang
Version: 1:3.8-36
Severity: important

Dear Maintainer,

clang and clang++ ccache symlink are missing :

$ ls -l /usr/lib/ccache/ 
total 0
lrwxrwxrwx 1 root root 16 mars   4 11:49 c++ -> ../../bin/ccache
lrwxrwxrwx 1 root root 16 mars   4 11:49 c89-gcc -> ../../bin/ccache
lrwxrwxrwx 1 root root 16 mars   4 11:49 c99-gcc -> ../../bin/ccache
lrwxrwxrwx 1 root root 16 mars   4 11:49 cc -> ../../bin/ccache
lrwxrwxrwx 1 root root 16 mars   4 11:49 g++ -> ../../bin/ccache
lrwxrwxrwx 1 root root 16 mars   4 11:49 g++-6 -> ../../bin/ccache
lrwxrwxrwx 1 root root 16 mars   4 11:49 gcc -> ../../bin/ccache
lrwxrwxrwx 1 root root 16 mars   4 11:49 gcc-6 -> ../../bin/ccache
lrwxrwxrwx 1 root root 16 mars   4 11:49 i686-linux-gnu-g++ -> ../../bin/ccache
lrwxrwxrwx 1 root root 16 mars   4 11:49 i686-linux-gnu-g++-6 -> 
../../bin/ccache
lrwxrwxrwx 1 root root 16 mars   4 11:49 i686-linux-gnu-gcc -> ../../bin/ccache
lrwxrwxrwx 1 root root 16 mars   4 11:49 i686-linux-gnu-gcc-6 -> 
../../bin/ccache


Christian

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

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

Versions of packages clang depends on:
ii  clang-3.8  1:3.8.1-24

clang recommends no packages.

clang suggests no packages.

-- no debconf information

Bug#866226: systemd 233 breaks docker with "no subsystem for mount" error

[Laurent Bigonville]

On Wed, 28 Jun 2017 16:54:40 +0200 Jeroen Verellen 
 wrote:


> Dear Maintainer,

Hi,

>
> I have an issue after the latest update of systemd. It seems to be 
similar as https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843509

>
> When starting a docker container I get the following:
>
> docker start mysql
> Error response from daemon: oci runtime error: 
container_linux.go:247: starting container process caused 
"process_linux.go:359: container init caused \"rootfs_linux.go:54: 
mounting \\\"cgroup\\\" to rootfs 
\\\"/var/lib/docker/overlay2/177270b60c5ab19437e45fc913e4242b89b8e1ed5913c707563cc9c4850512e2/merged\\\" 
at \\\"/sys/fs/cgroup\\\" caused \\\"no subsystem for mount\\\"\""

> Error: failed to start containers: mysql

The bug is in the runc package and is already fixed upstream but not in 
debian (see: #856951).


As a workaround you might want to add 
"systemd.legacy_systemd_cgroup_controller=yes" to the kernel options at boot


Regards,

Laurent Bigonville

Bug#743179: the order of syntax definitions in nanorc matters

[bernward . pub]

Hello Benno, thank you.

I checked the regexes and could not find any clou,
that the regex for awk could catch shell scripts:

from my awk.nanorc:

syntax "awk" "\.a:wk$"
header "^#!/usr/bin/g?awk"

If a wrong regex would be the cause of the problem, the effect should be 
a wrong syntax highlighting, but not just _no_ highlighting.

(by the way, my current nano version is 2.2.6, while the man page for 
nanorc is version 2.0.0 from August 23, 2007 and does not include a 
description of the header-command. But /usr/share/nano/sh.nanorc does 
use it:

header "^#!.*/(ba|k|pdk)?sh[-0-9_]*"

so I assume, I may use it too for my awk.nanorc)


In the meantime, I found two things which seem noteworthy,
one information and one rumour:

1) on the nano home page, the recommendation for the current version 2.8 
to build a user specific .nanorc still suggests to copy the 
sample.nanorc to start with, which is the same as copying /etc/nanorc 
[https://www.nano-editor.org/dist/v2.8/faq.html#3.9a]. This means, that 
puting only selected commands in .nanorc ist _not_ recommended.

2) On https://github.com/nanorc/nanorc I found an anonymous rumour: 
„There appears to be a bug in older versions of nano that causes 
highlighting to fail when /etc/nanorc and ~/.nanorc both contain syntax 
rules. The usual workaround is to remove all syntax and include commands 
from one file or the other, or to use a newer version of nano.“ But I 
could not find a reference for this statement nor a version, for which 
it should be valid.


Regards, Bernward.

Bug#866230: /etc/bash_completion.d/dput file not removed on upgrade

[Laurent Bigonville]

Package: dput
Version: 0.12.1
Severity: normal

Hi,

It seems that the package is moving the bash completion file from
/etc/bash_completion.d/ to /usr/share/bash-completion/completions but
the file in /etc is not remved on upgrade.

The package should explicitly remove that file on upgrade

Regards,

Laurent Bigonville

-- 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.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages dput depends on:
ii  python2.7.13-2
ii  python-debian 0.1.30
ii  python-gpg1.8.0-3+b2
ii  python-pkg-resources  36.0.1-1

dput recommends no packages.

Versions of packages dput suggests:
ii  lintian 2.5.51
pn  mini-dinstall   
ii  openssh-client  1:7.5p1-5
ii  rsync   3.1.2-2

-- Configuration Files:
/etc/bash_completion.d/dput [Errno 2] Aucun fichier ou dossier de ce type: 
'/etc/bash_completion.d/dput'

-- no debconf information

Bug#866229: /etc/initramfs-tools/hooks/reiserfsprogs not removed on upgrade

[Laurent Bigonville]

Package: reiserfsprogs
Version: 1:3.6.25-5
Severity: normal

Hi,

It seems that the package is moving the
/etc/initramfs-tools/hooks/reiserfsprogs file to
/usr/share/innitramfs-tools/hooks which is a good thing, but the file in
/etc is not remved on upgrade.

The package should explicitly remove that file on upgrade

Regards,

Laurent Bigonville

-- 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.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages reiserfsprogs depends on:
ii  libc6   2.24-12
ii  libcomerr2  1.43.4-2
ii  libuuid12.29.2-1

reiserfsprogs recommends no packages.

reiserfsprogs suggests no packages.

-- no debconf information

Bug#866127: initramfs-tools: Please allow fully disabling initramfs generation

[Balint Reczey]

Hi Ben,

On Tue, Jun 27, 2017 at 7:30 PM, Ben Hutchings  wrote:
> Control: tag -1 wontfix
>
> This is already allowed, and I don't think any new setting is needed.
>
> On Tue, 2017-06-27 at 17:56 +0200, Balint Reczey wrote:
>> Package: initramfs-tools
>> Version: 0.130
>> Severity: wishlist
>> Tags: patch
>>
>> Hi,
>>
>> Setting update_initramfs=no in update-initramfs.conf still triggers
>> initramfs creation on kernel updates.
>> While this generally makes sense some systems don't need initramfs to
>> boot and currently there is
>> no nice way of fully disabling initramfs generation.
>
> Debian's official kernel packages won't boot on any system without an
> initramfs.  That's why they depend on an initramfs generator.
>
>> The attached patch introduces update_initramfs=never which skips
>> initramfs generation even when the kernel is upgraded. Please consider
>> accepting it in a future upload.
>
> I already split initramfs-tools into two binary packages precisely so
> that you can have the tools installed without automatically building an
> initramfs for every installed kernel.  (Although that was actually done
> to allow coexistence with dracut.)
>
> Custom kernels that are meant to work without an initramfs should have
> CONFIG_BLK_DEV_INITRD disabled; then the postinst script generated by
> 'make deb-pkg' will set INITRD=No which effectively disables the
> initramfs-tools (and dracut) postinst hook.
>
> If Ubuntu's official kernel packages can boot without an initramfs on
> some systems, then the package relations should be changed so that they
> Recommend, rather than Depend-ing on, an initramfs generator.

Thanks, this is indeed the clean solution.

Cheers,
Balint

-- 
Balint Reczey
Debian & Ubuntu Developer

Bug#866160: closed by Gianfranco Costamagna <locutusofb...@debian.org> (Re: Bug#866160: RFS: moka-icon-theme/5.3.6-1)

[foss.freedom]

Hi Gianfranco,

  many thanks for sponsoring this.

Quick question.  I can see the moka-icon-theme v5.6.1 source has
entered the unstable archive - but I don't see the built binary
(_all.deb).

http://cdn-fastly.deb.debian.org/debian/pool/main/m/moka-icon-theme/

Any idea where the binary has gone?  I presume that is the reason why
the package hasnt sync'd to launchpad.net

thanks in advance

David

On 27 June 2017 at 20:42, Debian Bug Tracking System
 wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the sponsorship-requests package:
>
> #866160: RFS: moka-icon-theme/5.3.6-1
>
> It has been closed by Gianfranco Costamagna .
>
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Gianfranco Costamagna 
>  by
> replying to this email.
>
>
> --
> 866160: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866160
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>
>
> -- Forwarded message --
> From: Gianfranco Costamagna 
> To: "foss.freedom" , <866160-d...@bugs.debian.org>
> Cc:
> Bcc:
> Date: Tue, 27 Jun 2017 19:38:57 + (UTC)
> Subject: Re: Bug#866160: RFS: moka-icon-theme/5.3.6-1
> hello,
>
>
>>  I am looking for a sponsor for my package "moka-icon-theme"
>
>
> I like it
>
> G.
>
> -- Forwarded message --
> From: "foss.freedom" 
> To: Debian Bug Tracking System , Adam Borowski 
> 
> Cc:
> Bcc:
> Date: Tue, 27 Jun 2017 20:16:34 +0100
> Subject: RFS: moka-icon-theme/5.3.6-1
> Package: sponsorship-requests
> Severity: normal
>
>   Dear mentors,
>
>   I am looking for a sponsor for my package "moka-icon-theme"
>
>  * Package name: moka-icon-theme
>Version : 5.3.6-1
>Upstream Author : Sam Hewitt 
>  * URL : github.com/snwh/moka-icon-theme
>  * License : GPL-3+/CC-BY-SA-4.0
>Section : misc
>
>   It builds those binary packages:
>
> moka-icon-theme - Tango-esque desktop icon set called Moka
>
>   To access further information about this package, please visit the
> following URL:
>
>   https://mentors.debian.net/package/moka-icon-theme
>
>
>   Alternatively, one can download the package with dget using this command:
>
> dget -x 
> https://mentors.debian.net/debian/pool/main/m/moka-icon-theme/moka-icon-theme_5.3.6-1.dsc
>
> Notes:
>   have run linitian -i -I on the built .changes
>   I have run check-all-the-things to confirm that no additional
> copyright reconciliation is required
>
>   Changes since the last upload:
>
> * new upstream release
> - variety of new icons: elasticsearch, wxhexeditor,
>   wxformbuilder, gtkhash, internet archive, zenmap,
>   ubuntu-budgie, laptop-mode-tools, atlassian services,
>   TI code composer studio
> - symlinks for apps that are comparable i.e. tilix > terminix,
>   nmap > zenmap, budgie-remix > ubuntu-budgie,
>   regedit > wine, wine-regedit > wine
>   * Packaging Changes:
> - drop patch fix-overly-large-icons since this is now incorporated
>   with the release
> - change debhelper and compat to v10
> - update VCS fields from budgie-remix to UbuntuBudgie
> - update copyright field year from 2016 to 2016-2017
>
>
>
>   Regards,
>David Mohammed
>

Bug#866166: sagemath: FTBFS with Sphinx 1.5: AttributeError: 'BuildEnvironment' object has no attribute 'citations'

[Dmitry Shachnev]

Hi Tobias, and thanks for the quick response!

On Wed, Jun 28, 2017 at 02:44:23PM +0100, Tobias Hansen wrote:
> Hi Dmitry,
>
> would it be an option to upload sphinx 1.5 to unstable together with
> sagemath 8.0 (which works fine with sphinx 1.5) or do you want to do it
> before? We plan to upload sagemath 8.0 to unstable when it's released
> (they are at beta12 now).

That depends on how long do you estimate the final release to take.

From what I found [1] the sage-8.0 milestone still has 341 active issues,
which does not sound very optimistic.

I can wait for 2 or 3 weeks, but I do not want to wait longer. After all
upstream already released Sphinx 1.6 so we are two major releases behind.

> Otherwise it's a matter of backporting commits from sagemath 8.0 to 7.6.

I think this is not enough, unless the second part of my bugreport is also
addressed upstream.

[1]: https://trac.sagemath.org/milestone/sage-8.0

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Bug#848121: [Pkg-sysvinit-devel] Bug#848121: File conflict between manpages and initscripts

[Dr. Tobias Quathamer]

Am 17.12.2016 um 02:26 schrieb Michael Biebl:
> Am 16.12.2016 um 22:16 schrieb Dr. Tobias Quathamer:
>> I've prepared a patch for the git repository on alioth, please review
>> it. The patch should cover all places where tmpfs(5) is mentioned,
>> except debian/changelog.
>>
>> The package builds in a sid chroot without problems.
>>
>> If everybody thinks that this change is acceptable, it would be great to
>> get it into Stretch ...
> 
> lgtm, thanks Tobias

Dear all,

obviously, the patch did not make it into stretch, but I'd like to ask
again about a possible resolution for buster.

@Ian, you seem to be adopting the package. As you've stated earlier in
this bug report, you're willing to rename the manpage from tmpfs.5 to
tmpfs-config.5. Is the patch I've sent acceptable for you?

Regards,
Tobias




signature.asc
Description: OpenPGP digital signature

Bug#866228: debian-edu-config: fails to configure apache2 debian-edu-userdir module

[Wolfgang Schweer]

Package: debian-edu-config
Version: 1.929
Severity: important

After a Jessie -> Stretch upgrade of a system with profiles 
'Main-Server' and 'Workstation' personal web pages www/~ 
stopped working. The cause is a wrong link configuration in cf.apache2,
introduced in version 1.929.

This patch would fix it; please check and test. (In addition the apache2 
default userdir module is disabled and the comment is improved.)

diff --git a/cf/cf.apache2 b/cf/cf.apache2
index 6296ea1c..9b5191a4 100644
--- a/cf/cf.apache2
+++ b/cf/cf.apache2
@@ -1,13 +1,16 @@
 links:
   debian.server.installation::
 /etc/php/apache2/php.ini ->! /etc/php/apache2/php-debian-edu.ini
-/etc/apache2/mods-available/userdir.load ->! 
/etc/apache2/mods-available/debian-edu-userdir.load
+/etc/apache2/mods-available/debian-edu-userdir.load ->! 
/etc/apache2/mods-available/userdir.load
 
 shellcommands:
   debian.server.installation::
   # Generate the snakeoil selfsigned certificate using the make-ssl-cert 
tool
   "/usr/sbin/make-ssl-cert generate-default-snakeoil"
-  # Enabling userdir, create a directory ~/public_html to make it 
available on web as http://tjener.intern/~username.
+  # Disable default userdir.
+  "/usr/sbin/a2dismod userdir"
+  # Enabling debian-edu-userdir; create a directory ~/public_html
+  # to make it available as https://www/~.
   "/usr/sbin/a2enmod debian-edu-userdir"
   # Enabling ssl
   "/usr/sbin/a2enmod ssl"


Wolfgang


signature.asc
Description: PGP signature

Bug#865869: debhelper: Don't run dh_installdocs if nodoc is specified in DEB_BUILD_PROFILES

[Chris Lamb]

Hi,

> the suggested work around for now is not policy compliant.

Well spotted. Would that matter though? I mean, nobody should be uploading
packages to Debian with nodoc anyway, surely?


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb, Debian Project Leader
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#866227: runescape: Use a better icon file format

[asciiwolf]

Package: runescape
Version: 0.1-4
Severity: normal
Tags: patch

The current xpm icon has issues with appstream-generator on Ubuntu and 
RuneScape cannot be found and/or installed using GNOME Software (or another 
AppStream GUI) because of this. I have included a png file converted from the 
xpm and a desktop file patch as attachment.

runescape.desktop.patch
Description: Binary data

Bug#865102: jessie-pu: package libdvdnav/5.0.1-1+deb8u1

[Mike Gabriel]

Hi,

On  Di 27 Jun 2017 06:18:05 CEST, Cyril Brulebois wrote:


Control: tag -1 confirmed

Mike Gabriel  (2017-06-19):

Attached is a .debdiff that fixes various crashes when playing DVDs in VLC.
The DVD mostly starts playing for some time, but crashes some 5-10 minutes
after the DVD has been started playing. With the attached change, no crashes
are observed anymore.

The issue is resolved in stretch, but still open in jessie. Please consider
accepting this change via jessie-pu. Thanks.


Looks good to me, feel free to upload; thanks.


There is an update for one uploader in the .debdiff. This one is of
course optional, but preferred.


OK.


KiBi.


the package has just been uploaded (by mfv@d.o).

Thanks!
Mike
--

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

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



pgpPVmrhySaY1.pgp
Description: Digitale PGP-Signatur

Bug#866225: biboumi: Dependencies on libubsan and libasan

[Florent Le Coz]

Package: biboumi
Version: 5.0-1
Severity: normal

Dear Maintainer,

Biboumi output .deb currently depends on libasan3 and libubsan0, but these 
dependencies are only useful in debug mode.
This makes the software slower and heavier (a package without these 
dependencies weighs only 300Ko instead of the current 2.7Mo).

To fix this, I applied this patch on my own copy:

https://lab.louiz.org/louiz/biboumi/commit/76f5fa81f2026770c907bee0e931aae8d8c7a1bd

Biboumi's build process disables the libasan, libubsan and the coverage tools, 
when it is build in Release mode.


I have my own build process where you can see the differences:

Before (as it is in debian sid at the moment):
https://lab.louiz.org/louiz/biboumi/-/jobs/8416/raw
And the output .deb: 
https://lab.louiz.org/louiz/biboumi/-/jobs/8416/artifacts/browse

After (with the patch applied):
https://lab.louiz.org/louiz/biboumi/-/jobs/8418/raw
And the output .deb: 
https://lab.louiz.org/louiz/biboumi/-/jobs/8418/artifacts/browse


So, it should be built with -DCMAKE_BUILD_TYPE=Release


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

Kernel: Linux 4.9.3-200.fc25.x86_64 (SMP w/12 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968), LANGUAGE=C 
(charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

Versions of packages biboumi depends on:
ii  libasan3 6.3.0-19
ii  libc62.24-11
ii  libexpat12.2.1-2
ii  libgcc1  1:7.1.0-7
ii  libgcrypt20  1.7.6-2
ii  libidn11 1.33-1
ii  libstdc++6   7.1.0-7
ii  libsystemd0  232-25
ii  libubsan07.1.0-7
ii  libudns0 0.4-1+b1
ii  libuuid1 2.29.2-1

biboumi recommends no packages.

biboumi suggests no packages.

-- no debconf information

Bug#850890: patch

[solo-debianbugs]

Control: tags -1 + patch

Attached is a trivial patch which fixes the build on OpenSSL 1.1.

Chris.
diff --git a/opennebula-4.12.3+dfsg/debian/control b/opennebula-4.12.3+dfsg/debian/control
index 5cd7e8e..df9dc68 100644
--- a/opennebula-4.12.3+dfsg/debian/control
+++ b/opennebula-4.12.3+dfsg/debian/control
@@ -11,7 +11,7 @@ Build-Depends: debhelper (>= 9), dh-systemd, dh-linktree, javahelper
   ,flex
   ,libmysql++-dev
   ,libsqlite3-dev
-  ,libssl1.0-dev
+  ,libssl-dev
   ,libws-commons-util-java
   ,libxml2-dev
   ,libxmlrpc-c++8-dev
diff --git a/opennebula-4.12.3+dfsg/src/common/NebulaUtil.cc b/opennebula-4.12.3+dfsg/src/common/NebulaUtil.cc
index 90a0a17..f528998 100644
--- a/opennebula-4.12.3+dfsg/src/common/NebulaUtil.cc
+++ b/opennebula-4.12.3+dfsg/src/common/NebulaUtil.cc
@@ -154,18 +154,18 @@ string * one_util::base64_decode(const string& in)
 
 string one_util::sha1_digest(const string& in)
 {
-EVP_MD_CTX mdctx;
+EVP_MD_CTX *mdctx;
 unsigned char  md_value[EVP_MAX_MD_SIZE];
 unsigned int   md_len;
 ostringstream  oss;
 
-EVP_MD_CTX_init();
-EVP_DigestInit_ex(, EVP_sha1(), NULL);
+mdctx = EVP_MD_CTX_new();
+EVP_DigestInit_ex(mdctx, EVP_sha1(), NULL);
 
-EVP_DigestUpdate(, in.c_str(), in.length());
+EVP_DigestUpdate(mdctx, in.c_str(), in.length());
 
-EVP_DigestFinal_ex(,md_value,_len);
-EVP_MD_CTX_cleanup();
+EVP_DigestFinal_ex(mdctx,md_value,_len);
+EVP_MD_CTX_free(mdctx);
 
 for(unsigned int i = 0; i

Bug#866224: Fwd: gimp-gap 2.6.0 is wrong for gimp 2.8.x

[mc]

Package: gimp-gap

Version: 2.6.0+dfsg-5+b2

from

https://bugzilla.gnome.org/show_bug.cgi?id=749290

Note that the GIT master was still compatible with the older GIMP-2.6.x 
releases

until 2015.05.14, but since this date it has been updated to the level of
the gap-2-8 branch.
Note that GIT master is now intended for further updates
to follow GIMP-2.9.x and later API changes.




Now Now master and 2.8 gimp-gap branches are the same.

gimp-gap 2.6.0 is broken in many functions with gimp 2.8.xx




Regards

Bug#865869: debhelper: Don't run dh_installdocs if nodoc is specified in DEB_BUILD_OPTIONS

[Niels Thykier]

On Sun, 25 Jun 2017 13:31:40 +0100 Chris Lamb  wrote:
> Package: debhelper
> Version: 10.2.5
> Severity: wishlist
> 
> Hi,
> 
> I just added the following to the python-django packaging's debian/rules
> file:
> 
> ifneq (,$(filter nodoc,$(DEB_BUILD_OPTIONS)))
> override_dh_installdocs:
> endif
> 
> Wouldn't it make more sense for debhelper to do this by default? I see that
> debhelper does not really touch the build profiles at all, so this might be
> entirely deliberate.
> 
> 
> Regards,
> 
> -- 
>   ,''`.
>  : :'  : Chris Lamb, Debian Project Leader
>  `. `'`  la...@debian.org / chris-lamb.co.uk
>`-
> 
> 


JFR (as requested per IRC), the suggested work around for now is not
policy compliant.  The policy mandates that copyright + changelog files
(among other) basic documentation is still installed under "nodoc".
  As dh_installdoc installs the copyright file, the above snippet
(without anything else) would omit the copyright file from the packages.

Thanks,
~Niels

Bug#845659: debpatch: New script, "Apply a debdiff to a Debian source package"

[Ximin Luo]

Ximin Luo:
> James McCoy:
>> On Thu, Jan 05, 2017 at 04:18:00PM +, Ximin Luo wrote:
>>> Ximin Luo:
 As part of the Reproducible Builds effort, I've written a tool called
 debpatch(1), see the branch here:
 [..]
>>>
>>> Hi devscripts team,
>>>
>>> Any news on this?
>>
>> Apologies for not giving this a review sooner.
>>
>>> I would also be happy to merge this myself (I have
>>> the access) but I thought it would be good to ask for a review first,
>>> since I haven't contributed to this repo before.
>>
>> I agree with Sean that it would be good to not to have another
>> reimplementation of changelog merging.  However, if dpkg-mergechangelogs
>> doesn't provide the functionality you need, I would recommend looking at
>> python3-debian's debian.changelog module.  I think that would probably
>> be easier than trying to twist dch into doing the work.
>>
> 
> Sorry for the delay, I have now made these changes.
> 
> dpkg-mergechangelogs seemed interesting but actually does a different job - 
> it merges different entries by total ordering on Debian version numbers, and 
> it does a normal 3-way merge when changes to the same entry are detected. 
> This type of merging seems more suited to packages that have already been 
> released. For example, it was unable to merge my pu/debpatch branch with the 
> current master, and I had to resolve that manually.
> 
> OTOH debpatch is for rebasing unreleased changes on top of new released 
> packages. So what we want here is to plonk any added extra changelog entry, 
> on top of the new base, and adjust the version number accordingly.
> 
> I have switched to using debian.changelog though, thanks for the tip. I also 
> got rid of some dirty "this is already applied" logic and removed some 
> arbitrary limits.
> 
> https://anonscm.debian.org/cgit/collab-maint/devscripts.git/log/?h=pu/debpatch
> 
> Pushed there ^ but also would be happy to squash these commits if you prefer.
> 

I've updated git (pu/debpatch branch) with a few more minor changes.

Is it OK if I merge this into master now?

X

-- 
GPG: ed25519/56034877E1F87C35
GPG: rsa4096/1318EFAC5FBBDBCE
https://github.com/infinity0/pubkeys.git

Bug#866221: postgresql-9.4-postgis-2.1 uninstallable under Stretch

[Élie Bouttier]

Hello Markus,

I successfully upgraded to postgresql 9.6 using
postgresql-9.4-postgis-2.3 from PgApt (and some ALTER EXTENSION postgis
UPDATE TO "2.3.2"; in relevant databases).

Thank you very much for your answer.

Best Regards,

Élie Bouttier

On 28/06/2017 15:59, Markus Wanner wrote:
> Hello Élie,
> 
> On 06/28/2017 03:28 PM, Élie Bouttier wrote:
>> I upgraded from Jessie with postgresql-9.4 to Stretch which brings 
>> postgresql-9.6.
>> The postgresql-9.4 package from Jessie is still installable under Stretch in 
>> order to run the pg_upgradecluster utility.
>> However, my cluster is half-broken, the postgresql-9.4-postgis-2.1 having 
>> been uninstalled (and postgresql-9.6-postgis-2.3 installed).
> 
> that's what the pgapt [0] repository is for. Please try installing
> postgresql-9.4-postgis-2.1 (for stretch) from there.
> 
>> I suppose the postgresql-9.4-postgis-2.1 package should be installable under 
>> Stretch (like postgresql-9.4) to allow an cluster update.
> 
> No, postgresql-9.4-postgis-2.1 from jessie is expected to be compiled
> and work for jessie, not stretch.
> 
> The problem basically is that Debian only ever supports a single
> Postgres (major) version, where as you need to have multiple installed
> in parallel for upgrades (with reasonably short downtimes).
> 
> Please let us know if pgapt is a feasible solution for you and whether
> or not the upgrade worked with the postgis package from there.
> 
> Kind Regards
> 
> Markus Wanner
> 
> 
> [0]: PgApt
> https://wiki.postgresql.org/wiki/Apt
> 

Bug#864291: samba: CVE-2017-9461: infinite loop on bad-symlink resolution

[Hugo Lefeuvre]

Hi,

I couldn't reproduce this bug in the wheezy version and I think it
isn't affected.

I get the following error message:

$ smbclient //server/share -c "posix; symlink nothing broken"
(...)
$ smbclient //localhost/shareddir -c "put /etc/issue broken"
Domain=[WORKGROUP] OS=[Unix] Server=[Samba 3.6.6]
NT_STATUS_OBJECT_NAME_NOT_FOUND opening remote file \broken

In the wheezy version, the fd_open_atomic function doesn't exist and
the existing fd_open function doesn't use loops.

Regards,
 Hugo

-- 
 Hugo Lefeuvre (hle)|www.owl.eu.com
4096/ ACB7 B67F 197F 9B32 1533 431C AC90 AC3E C524 065E


signature.asc
Description: PGP signature

Bug#866114: texlive-fonts-extra: Icon errors when installed alongside fonts-font-awesome

[Norbert Preining]

Hi Connor,

> to specifically remove the fonts-extra problem doesn't fix things which
> seems to indicate the problem is with another part of texlive-full. Do you

No, probably not texlive-full, but with some fonts being installed.

> know of anything else I can check to iron out what might be causing the
> problem? Running
> 
> $ fc-list | grep -i awesome
> 
> gives me the same output as you.

And what about uninstalling all of texlive-full, and also all depending
packages, and see what happens then?

I have no idea, but TeX Live does not interfer in this area, it adds
*some* fonts to the fontconfig path, but not all of it, and awesome
is not included.

All the best

Norbert

--
PREINING Norbert   http://www.preining.info
Accelia Inc. +JAIST +TeX Live +Debian Developer
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#856850: biboumi FTBFS on big endian: test failure

[Jonas Smedegaard]

Quoting Jonas Smedegaard (2017-06-28 16:08:38)
> Quoting Florent Le Coz (2017-06-28 15:43:48)
>> If I understand correctly, since buster is not frozen yet, the sid 
>> (unstable) package should go into testing (buster) automatically in a 
>> few days/weeks, right?
>> 
>> Anyway, if you want help backporting this fix, let me know. And if 
>> you want to just package the 5.0, you can probably close this bug 
>> report.
> 
> Thanks for the bugreport!
> 
> I have (separately, a moment ago) tagged this bugreport with affected 
> version and known solved one, and (because I suspect the "fixed" hint is 
> not really enough) with this post formally closing it.

Sorry, posted too quickly.

Thanks but no need for your help backporting the bugfix: As you 
correctly guessed, the version now in Sid will automatically replace the 
one in Buster.  Only if someone filed a bugreport against the version in 
Sid would autoamtic transition not kick in, but in this case my added 
hinting should help keep the transition going ;-)


 - Jonas

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

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


signature.asc
Description: signature

Bug#866085: At least it should be the option to not download

[Lennart Sorensen]

On Wed, Jun 28, 2017 at 08:52:31AM +0200, Narcis Garcia wrote:
> If you *will* be connected to the internet you *will* need to install
> security updates;
> Internet is not the only source for packages (). If someone
> installs Debian on 3 computers (or repeats installation 3 times), it
> shouldn't mean to use 3x internet traffic repeating installer downloads.
> 
> A) This user can save and reuse packages cache and apply updates at the
> convenient moment.
> B) When repeating install at the same computer (e.g. changing install
> decisions such as partitioning, architecture, etc.) the user only needs
> updates on final one.
> 
> Most of internet uses on the world have really low bandwidth accessing
> to the internet, and making (some) unnecessary downloads can be a money
> & time problem.
> 
> +
> I've participated on an "install party" where only half of Debian
> installs could be done because of this issue.

If you are doing an install party, set up a proxy server.  That really
really helps a lot.

-- 
Len Sorensen

Bug#865560: RFS: gexiv2/0.10.6-1

[Gianfranco Costamagna]

hurray!


>I didn't notice this when I ran the tests because I already have
>libexiv2-dev installed.  I see now that I could have run the tests in an

>sbuild schroot.

another issue fixed by a good testsuite!

however not quite ready 
http://debomatic-amd64.debian.net/distribution#unstable/gexiv2/0.10.6-1/autopkgtest
G.

Bug#865366:

[shan...@gmail.com]

Hello, this error has being fixed in dosbox SVN. You'll need to wait until
that release it packaged in debian.
See also: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825604

Bug#702773: libcidr: changing back from ITP to RFP

[Santiago]

El 28/06/17 a las 18:59, Daniil Baturin escribió:
> Hi Santiago,
> 
> If you are ready to sponsor it, I'm definitely going to resurrect that
> packaging effort (I still have the files, I'm pretty sure they will need
> some updates for the newer packaging standards, since myself I only
> cared about making it buildable for my own use).

Please, go ahead! :-)
Could you please upload it to mentors, again?

> One of the things I'm using it for myself is
> https://github.com/vyos/ipaddrcheck , which I also would like to
> contribute to Debian, but it can only be done when libcidr is there.

We'll see that once libcidr is in Debian then.

> 
> On a side note, it would be nice if most of the quality assurance
> process could  be done without human intervention so that potential
> sponsors would instantly know if they aree going to work with packaging
> that is violating the guidelines or is outright broken or not.

Indeed. That would be very helpful.

Cheers!

  -- Santiago


signature.asc
Description: PGP signature

Bug#866221: postgresql-9.4-postgis-2.1 uninstallable under Stretch

[Markus Wanner]

Hello Élie,

On 06/28/2017 03:28 PM, Élie Bouttier wrote:
> I upgraded from Jessie with postgresql-9.4 to Stretch which brings 
> postgresql-9.6.
> The postgresql-9.4 package from Jessie is still installable under Stretch in 
> order to run the pg_upgradecluster utility.
> However, my cluster is half-broken, the postgresql-9.4-postgis-2.1 having 
> been uninstalled (and postgresql-9.6-postgis-2.3 installed).

that's what the pgapt [0] repository is for. Please try installing
postgresql-9.4-postgis-2.1 (for stretch) from there.

> I suppose the postgresql-9.4-postgis-2.1 package should be installable under 
> Stretch (like postgresql-9.4) to allow an cluster update.

No, postgresql-9.4-postgis-2.1 from jessie is expected to be compiled
and work for jessie, not stretch.

The problem basically is that Debian only ever supports a single
Postgres (major) version, where as you need to have multiple installed
in parallel for upgrades (with reasonably short downtimes).

Please let us know if pgapt is a feasible solution for you and whether
or not the upgrade worked with the postgis package from there.

Kind Regards

Markus Wanner


[0]: PgApt
https://wiki.postgresql.org/wiki/Apt



signature.asc
Description: OpenPGP digital signature

Bug#859717: Skipfish uses deleted openssl functionality

[solo-debianbugs]

One of the failures here is using SSL_CIPHER->algo_strength,
which has been removed with, as far as I can see, no replacement.

I've raised a bug against OpenSSL upstream to consider exposing this:
https://github.com/openssl/openssl/issues/3795

Chris.

Bug#856850: biboumi FTBFS on big endian: test failure

[Florent Le Coz]

Note that this bug has been fixed upstream, in the 5.0 release.

See the specific commit:

https://lab.louiz.org/louiz/biboumi/commit/99a4ddedaf903d27b781341108433ae2d9533ad1

I see that Buster still contains only version 4.3, but Sid already has 
5.0, so I don’t exactly know if you want to continue supporting the 4.x 
release or not.
If I understand correctly, since buster is not frozen yet, the sid 
(unstable) package should go into testing (buster) automatically in a 
few days/weeks, right?


Anyway, if you want help backporting this fix, let me know. And if you 
want to just package the 5.0, you can probably close this bug report.


--
Florent

Bug#862481: jessie-pu: package xfce4-weather-plugin/0.8.3-2

[Yves-Alexis Perez]

On Wed, 2017-06-28 at 15:13 +0200, Emilio Pozuelo Monfort wrote:
> On 28/06/17 12:38, Yves-Alexis Perez wrote:
> > On Wed, 2017-06-28 at 00:24 +0200, Cyril Brulebois wrote:
> > > This looks good to me (also tested locally without then with the patch
> > > series). Feel free to upload, targetting jessie; thanks.
> > 
> > Thanks! Should I target 'jessie' (not recognized by dch -r) or 'oldstable-
> > proposed-updates'?
> 
> jessie. Can you file a bug against devscripts so codenames are recognized?

Done (#866223)
-- 
Yves-Alexis

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

Bug#866166: sagemath: FTBFS with Sphinx 1.5: AttributeError: 'BuildEnvironment' object has no attribute 'citations'

[Tobias Hansen]

Hi Dmitry,

would it be an option to upload sphinx 1.5 to unstable together with
sagemath 8.0 (which works fine with sphinx 1.5) or do you want to do it
before? We plan to upload sagemath 8.0 to unstable when it's released
(they are at beta12 now).

Otherwise it's a matter of backporting commits from sagemath 8.0 to 7.6.

Best,
Tobias

On Tue, 27 Jun 2017 23:12:17 +0300 Dmitry Shachnev 
wrote:
> Source: sagemath
> Version: 7.6-2
> Severity: important
> User: python-modules-t...@lists.alioth.debian.org
> Usertags: sphinx1.5
> 
> Dear maintainer,
> 
> Sagemath fails to build with Sphinx 1.5 (available in experimental, but
> pending upload to unstable):
> 
>   # Sometimes, parts of the docbuild fail with MemoryError or OSError but
>   # Sage doesn't detect this. Here we detect it and fail the build if so.
>   ! grep Error sage/logs/dochtml.log
>   AttributeError: 'BuildEnvironment' object has no attribute 'citations'
>   WARNING: intersphinx inventory 
> '/<>/debian/build/usr/share/doc/sagemath/inventory/en/reference/objects.inv'
>  not fetchable due to : [Errno 2] No such file or 
> directory: 
> '/<>/debian/build/usr/share/doc/sagemath/inventory/en/reference/objects.inv'
>   AttributeError: 'BuildEnvironment' object has no attribute 'citations'
>   (repeats multiple times)
>   debian/rules:90: recipe for target 'check-dochtml-log' failed
> 
> This can be fixed by backporting upstream commit [1], but then it fails with
> dh_sphinxdoc error:
> 
>  debian/rules override_dh_sphinxdoc
>   make[1]: Entering directory '/<>'
>   dh_sphinxdoc -XMathJax.js -Xtranslations.js -Xsearchtools.js
>   dh_sphinxdoc: ignoring unknown JavaScript code: 
> debian/sagemath-doc-ca/usr/share/doc/sagemath/html/ca/intro/_static/mathjax_sage.js
>   dh_sphinxdoc: ignoring unknown JavaScript code: 
> debian/sagemath-doc-ca/usr/share/doc/sagemath/html/ca/intro/_static/thebe-sage.js
>   (more harmless warnings)
>   dh_sphinxdoc: 
> debian/sagemath-doc-en/usr/share/doc/sagemath/html/en/reference/_sources/sage/algebras/affine_nil_temperley_lieb.rst.txt
>  is missing
>   debian/rules:192: recipe for target 'override_dh_sphinxdoc' failed
> 
> This is most probably related to a change in Sphinx [2], which changed how
> searchtools.js looks for source files. dh_sphinxdoc now follows the same
> logic and expects to find these files in their new locations.
> 
> [1]: https://github.com/sagemath/sage/commit/78e671810360d3e0
> [2]: https://github.com/sphinx-doc/sphinx/pull/2454
> 
> --
> Dmitry Shachnev

Bug#866223: devscripts: Add support for codenames to dch

[Yves-Alexis Perez]

Package: devscripts
Version: 2.17.6
Severity: normal

Hi,

the stable release team ack'ed me a package upload to oldstable, and
requested that I target the upload to 'jessie'. Unfortunately, it seems
that debchangelog doesn't know about codenames:

=
corsac@scapa: dch -r -D jessie
dch warning: Recognised distributions are: unstable, testing, stable,
oldstable, experimental, {testing-,stable-,oldstable-,}proposed-updates,
{testing,stable,oldstable}-security, jessie-backports, stretch-backports
and UNRELEASED.
Using your request anyway.
dch: Did you see that warning?  Press RETURN to continue..
=

Could it be added at one point?

Thanks in advance and regards,
-- 
Yves-Alexis

-- Package-specific info:

--- /etc/devscripts.conf ---

--- ~/.devscripts ---
DEBSIGN_KEYID=71EF0BA8
DEBCHANGE_MULTIMAINT_MERGE=yes
DEBCHANGE_FORCE_SAVE_ON_RELEASE=yes
DEBCHANGE_RELEASE_HEURISTIC=changelog

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

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

Versions of packages devscripts depends on:
ii  dpkg-dev  1.18.24
ii  libc6 2.24-12
ii  libfile-homedir-perl  1.00-1
ii  perl  5.24.1-4
ii  python3   3.5.3-1

Versions of packages devscripts recommends:
ii  apt 1.4.6
pn  at  
ii  curl7.52.1-5
ii  dctrl-tools 2.24-2+b1
ii  debian-keyring  2017.05.28
ii  dput-ng [dput]  1.14
pn  equivs  
ii  fakeroot1.21-3.1
ii  file1:5.30-1
ii  gnupg   2.1.18-8
ii  libdistro-info-perl 0.15
ii  libdpkg-perl1.18.24
ii  libencode-locale-perl   1.05-1
pn  libgit-wrapper-perl 
pn  liblist-compare-perl
ii  liblwp-protocol-https-perl  6.06-2
ii  libsoap-lite-perl   1.20-1
ii  liburi-perl 1.71-1
ii  libwww-perl 6.15-1
ii  licensecheck3.0.29-1
ii  lintian 2.5.51
ii  man-db  2.7.6.1-2
ii  patch   2.7.5-1+b2
ii  patchutils  0.3.4-2
ii  python3-debian  0.1.30
ii  python3-magic   1:5.30-1
ii  sensible-utils  0.0.9
ii  strace  4.15-2
ii  unzip   6.0-21
ii  wdiff   1.2.2-2
ii  wget1.19.1-4
ii  xz-utils5.2.2-1.2+b1

Versions of packages devscripts suggests:
pn  adequate 
pn  autopkgtest  
pn  bls-standalone   
ii  bsd-mailx [mailx]8.1.2-0.20160123cvs-4
ii  build-essential  12.3
pn  check-all-the-things 
pn  cvs-buildpackage 
pn  devscripts-el
ii  diffoscope   83
pn  disorderfs   
pn  dose-extra   
pn  duck 
ii  faketime 0.9.6-7+b1
ii  gnuplot  5.0.5+dfsg1-7
ii  gpgv 2.1.18-8
pn  how-can-i-help   
pn  libauthen-sasl-perl  
pn  libfile-desktopentry-perl
pn  libnet-smtps-perl
pn  libterm-size-perl
ii  libtimedate-perl 2.3000-2
ii  libyaml-syck-perl1.29-1+b2
pn  mozilla-devscripts   
ii  mutt 1.8.3+neomutt20170609-2
ii  openssh-client [ssh-client]  1:7.5p1-5
pn  piuparts 
pn  ratt 
pn  reprotest
ii  svn-buildpackage 0.8.6
ii  w3m  0.5.3-34

-- no debconf information

Bug#866221: postgresql-9.4-postgis-2.1 uninstallable under Stretch

[Élie Bouttier]

Package: postgresql-9.4-postgis-2.1
Severity: normal

Dear Maintainer,

I upgraded from Jessie with postgresql-9.4 to Stretch which brings 
postgresql-9.6.
The postgresql-9.4 package from Jessie is still installable under Stretch in 
order to run the pg_upgradecluster utility.
However, my cluster is half-broken, the postgresql-9.4-postgis-2.1 having been 
uninstalled (and postgresql-9.6-postgis-2.3 installed).
The pg_upgradecluster utility refuse to upgrade my cluster due to the missing 
module:

pg_dump: [archiver (db)] query failed: ERROR:  could not access file 
"$libdir/postgis-2.1": No such file or directory

I tried reinstall postgresql-9.4-postgis-2.1 but apt refused:

The following packages have unmet dependencies:
 postgresql-9.4-postgis-2.1 : Depends: libgdal1h (>= 1.9.0) but it is not going 
to be installed
  Depends: libgeos-c1 (>= 3.4.2) but it is not 
going to be installed
  Depends: liblwgeom-2.1.4 (>= 2.1.2) but it is not 
going to be installed
E: Unable to correct problems, you have held broken packages.

I suppose the postgresql-9.4-postgis-2.1 package should be installable under 
Stretch (like postgresql-9.4) to allow an cluster update.


Sincerely,

Élie Bouttier


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

Kernel: Linux 4.9.0-3-amd64 (SMP w/1 CPU core)
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-9.4-postgis-2.1 depends on:
ii  libc6   2.24-11+deb9u1
pn  libgdal1h   
pn  libgeos-c1  
pn  liblwgeom-2.1.4 
pn  libproj0
ii  libxml2 2.9.4+dfsg1-2.2
ii  postgresql-9.4  9.4.12-0+deb8u1
ii  postgresql-9.4-postgis-scripts  2.1.4+dfsg-3

Versions of packages postgresql-9.4-postgis-2.1 recommends:
ii  postgis 2.3.1+dfsg-2
ii  postgresql-contrib-9.4  9.4.12-0+deb8u1

postgresql-9.4-postgis-2.1 suggests no packages.

Bug#863093: jessie-pu: package libwnckmm/0.1.1-1+deb8u1

[Cyril Brulebois]

Hi,

Samuel Thibault  (2017-06-28):
> Cyril Brulebois, on mer. 28 juin 2017 04:11:05 +0200, wrote:
> > Wait a minute, this adds a symlink and a dependency, but doesn't
> > remove anything; this doesn't look like a duplication fix?
> 
> ln -sf replaces the existing file with the symlink.

Sure, I know what ln -sf does. But the said file was never shipped in
the first place:

kibi@armor:/tmp/binary-libwnckmm-1.0-0-dev$ dpkg --contents 
libwnckmm-1.0-0-dev_0.1.1-1_amd64.deb | grep jquery.js
kibi@armor:/tmp/binary-libwnckmm-1.0-0-dev$ 

Indeed, after a build in a jessie chroot, there are plenty of references
to jquery.js in HTML files, but there's no jquery.js in the build tree.


KiBi.


signature.asc
Description: Digital signature

Bug#866207: inkscape: File Rendering in Inkscape is different when openning w/ software or ft png/pdf

[Luffah]

Hi Jonas,

On 28/06/2017 13:08, Jonas Smedegaard wrote:

Hi luffah,

Quoting luffah (2017-06-28 12:34:27)

Package: inkscape
Version: 0.92.1-1
Severity: normal

Dear Maintainer,
Thank you for your work, as i see the bug stack is high.
I had a problem which justify to rollback my version of inkscape.

* What led up to the situation?
 [regression]
 I had files working with previous version of Inkscape on Jessie.
 Now I open and modify the article like files,
 the render is ok in Inkscape, when i export to png the render
 still ok.
 But if i open the svg with an other file previewer (e.g. Comix
 wich is stable) or exporting to pdf, some CSS things are
 corrupted like text colors and offset.
* What outcome did you expect instead?
 I expect that Inkscape produce PDF output files which conserve
 the render.

Did opening in those same previewers/renderers produce different result
in the past

With the Jessie version of Inkscape,
i don't remember to experience these kind of problem.
That's why i use Inkscape in fact : i need to have a stable
result for producing documents.

It is difficult to compare, given i had made some copy pastes, and
moreover given version difference (inkscape 48 -> 92) which imply
change in file format.

My problem occur with color changing and text properties inside text block.

The good news
(after i uninstalled and tried unsuccesfully to compile
 and reinstalled Inkscape - and having installed Karbon aside),
are that i failed to reproduce the issue,
and that i found as a workaround to select and find the part of text 
with opacity

and modify the opacity.

So if the bug occur, it occurs rarely.
Therefore, I cannot state it is a regression.
The bug may be passed minor. (as a consequence of dist-upgrade ?)
I'll understood if you dismiss it.

Have a nice day.


You describe a bug regardless, but relevant to understand if it is a
regression.


  - Jonas

P.S. I am not the maintainer, just chiming in with a helpful followup
question.



  '-

Bug#866214: gdm3: there should be a note when 'slow keys' accessibility feature is enabled

[Emilio Pozuelo Monfort]

On 28/06/17 13:53, Martin Castillo wrote:
> Package: gdm3
> Version: 3.14.1-7
> Severity: minor
> 
> Dear Maintainer,
> 
> the 'slow keys' feature gives someone, who is not aware of it, the impression,
> that the keyboard is broken or that there is a software bug, either in the
> keyboard driver or the display manager.
> 
> Normally this is only enabled, when the user, that wants to use it, enables it
> himself. But on public systems, where multiple people use the same system 
> (like
> in a university), the following users will either think that the keyboard does
> not work, or if they find out, that long pressing works, that some software 
> has
> a problem.
> 
> I'd suggest, that you show a text noting that 'slow keys' is enabled, and
> optionally, how to turn it off. It would be like a note saying that caps lock
> is enabled.
> 
> For a long time one of the university computers had this 'problem' that no 
> one,
> not even
> the admins, knew how to fix. Today, I only found out by chance, that this was
> not a bug, but a feature.

Sounds like a good idea. It'd be good if you can report this upstream at

https://bugzilla.gnome.org/enter_bug.cgi?product=gdm

Thanks,
Emilio

Bug#866114: texlive-fonts-extra: Icon errors when installed alongside fonts-font-awesome

[Connor Glosser]

Hi Norbert -

Thanks for the help (and info!) After a little more investigating, I think
you're right -- this isn't a texlive-fonts-extra problem. I had assumed it
was because that's the only thing I know of in the TeX system that uses
font awesome, and the glyphs broke after I added texlive-full on a fresh
Stretch system that already had the i3 and fonts-font-awesome packages
installed (I can remove texlive-full and things work again). Running

$ sudo dpkg --remove --force-depends texlive-fonts-extra

to specifically remove the fonts-extra problem doesn't fix things which
seems to indicate the problem is with another part of texlive-full. Do you
know of anything else I can check to iron out what might be causing the
problem? Running

$ fc-list | grep -i awesome

gives me the same output as you.

Thanks!
~Connor

On Tue, Jun 27, 2017 at 10:13 AM, Norbert Preining 
wrote:

> tags 866114 + moreinfo
> thanks
>
> Hi Connor,
>
> > I use fontawesome to set workspace "icons" in my i3 window manager
> > config. If I only have the fonts-font-awesome package installed,
> > everything looks fine. However, when I install TeX, the fontawesome
> > glyphs no longer render properly in i3 (http://i.imgur.com/Js3Nfv1.png
> > -- should contain the firefox logo, the terminal icon, and a dot,
> > respectively).
>
> Hmmm, I am not sure whether this is a problem of texlive-fonts-extra.
> This package depends on
> fonts-font-awesome
> and links the .otf file into the texmf tree, so nothing changes here.
>
> In addition, it installs the type1 font version
> /usr/share/texlive/texmf-dist/fonts/type1/public/
> fontawesome/FontAwesome.pfb
> but this directory is not activated for X fonts. And even if it is,
> fontconfig should find the otf font, too, and deliver it.
>
> Do you have personal fontconfig configuration files that add specific
> directories to the fontconfig search path?
>
> In any case, can you use
> fc-list | grep -i awesome
> In my case I get:
> /usr/share/fonts/opentype/font-awesome/FontAwesome.otf:
> FontAwesome:style=Regular
> /usr/share/fonts/woff/font-awesome/fontawesome-webfont.woff:
> FontAwesome:style=Regular
> /usr/share/fonts/truetype/font-awesome/fontawesome-webfont.ttf:
> FontAwesome:style=Regular
> nothing that is touched at all by the TeX packages.
>
> All the best
>
> Norbert
>
> --
> PREINING Norbert   http://www.preining.info
> Accelia Inc. +JAIST +TeX Live +Debian Developer
> GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
>

Bug#866207: inkscape: File Rendering in Inkscape is different when openning w/ software or ft png/pdf

[Luffah]

Hi Jonas,

On 28/06/2017 13:08, Jonas Smedegaard wrote:

Hi luffah,

Quoting luffah (2017-06-28 12:34:27)

Package: inkscape
Version: 0.92.1-1
Severity: normal

Dear Maintainer,
Thank you for your work, as i see the bug stack is high.
I had a problem which justify to rollback my version of inkscape.

* What led up to the situation?
 [regression]
 I had files working with previous version of Inkscape on Jessie.
 Now I open and modify the article like files,
 the render is ok in Inkscape, when i export to png the render
 still ok.
 But if i open the svg with an other file previewer (e.g. Comix
 wich is stable) or exporting to pdf, some CSS things are
 corrupted like text colors and offset.
* What outcome did you expect instead?
 I expect that Inkscape produce PDF output files which conserve
 the render.

Did opening in those same previewers/renderers produce different result
in the past

With the Jessie version of Inkscape,
i don't remember to experience these kind of problem.
It is difficult to compare, given i had made some copy pastes, and
moreover given version difference (inkscape 48 -> 92) which imply
change in file format.

My problem occur with color changing and text properties inside text block.
A part of text  can have a property ignored by Inkscape but not on pdf 
export.

The good news is that i found as a workaround
to find with cursor the part of text with opacity
and remove it or more simply to use the menu "Text>Remove manuals kerns".

I cannot state it is a regression because :
- we can workaround the problem
- i have no evidence the problem didn't occur in previous versions
- given the problem focus on pdf export (which probably use external libs)

The bug may be passed minor.
I'll understood if you dismiss it.

Have a nice day.


You describe a bug regardless, but relevant to understand if it is a
regression.


  - Jonas

P.S. I am not the maintainer, just chiming in with a helpful followup
question.



  '-

Bug#866220: O: posterazor -- splits an image across multiple pages for assembly into a poster

[Simrun Basuita]

Package: wnpp
Severity: normal

Bug#862481: jessie-pu: package xfce4-weather-plugin/0.8.3-2

[Emilio Pozuelo Monfort]

On 28/06/17 12:38, Yves-Alexis Perez wrote:
> On Wed, 2017-06-28 at 00:24 +0200, Cyril Brulebois wrote:
>> This looks good to me (also tested locally without then with the patch
>> series). Feel free to upload, targetting jessie; thanks.
> 
> Thanks! Should I target 'jessie' (not recognized by dch -r) or 'oldstable-
> proposed-updates'?

jessie. Can you file a bug against devscripts so codenames are recognized?

Thanks,
Emilio