Bug#934015: O: asciidoc -- Highly configurable text format for writing documentation

[Joseph Herlant]

Package: wnpp
Severity: normal

I intend to orphan the asciidoc package.

The package description is:
 AsciiDoc is a text document format for writing articles, books, manuals and
 UNIX man pages. AsciiDoc files can be translated to HTML (with or without
 stylesheets), DocBook (articles, books and refentry documents) and LinuxDoc
 using the asciidoc command. AsciiDoc can also be used to build and maintain
 websites.
 .
 You write an AsciiDoc document the same way you would write a
 normal text document, there are no markup tags or weird format notations.
 AsciiDoc files are designed to be viewed, edited and printed directly or
 translated to other presentation formats
 .
 This metapackage provides a fully functionnal asciidoc environment working
 with dblatex for historical purposes.
 AsciiDoc is a text document format for writing articles, books, manuals and
 UNIX man pages. AsciiDoc files can be translated to HTML (with or without
 stylesheets), DocBook (articles, books and refentry documents) and LinuxDoc
 using the asciidoc command. AsciiDoc can also be used to build and maintain
 websites.
 .
 You write an AsciiDoc document the same way you would write a
 normal text document, there are no markup tags or weird format notations.
 AsciiDoc files are designed to be viewed, edited and printed directly or
 translated to other presentation formats


Currently there's a work to move it to python3 but it's not been released yet:
https://github.com/asciidoc/asciidoc-py3

Bug#934014: python3-demjson: missing Breaks+Replaces: python-demjson

[Andreas Beckmann]

Package: python3-demjson
Version: 2.2.4-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Selecting previously unselected package python3-demjson.
  Preparing to unpack .../python3-demjson_2.2.4-3_all.deb ...
  Unpacking python3-demjson (2.2.4-3) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python3-demjson_2.2.4-3_all.deb (--unpack):
   trying to overwrite '/usr/share/man/man1/jsonlint.1.gz', which is also in 
package python-demjson 2.2.4-2
  Errors were encountered while processing:
   /var/cache/apt/archives/python3-demjson_2.2.4-3_all.deb


cheers,

Andreas


python-demjson=2.2.4-2_python3-demjson=2.2.4-3.log.gz
Description: application/gzip

Bug#933997: gamemode isn't automatically activated for rise of the tomb raider

[Jonathan Carter]

On 2019/08/06 06:50, Axel Regnat wrote:
> Thanks for your fast response. I updated gamemode, libgamemode0 and
> libgamemodeauto0 to 1.4+git20190722.4ecac89-2 but that didn't change
> anything. I still need to set the launch option. I'm not experienced
> with git or salsa but I'm also unable to see any change there beside
> that you pushed new tags. Shouldn't there be a commit to re-enabling the
> daemon?

Ah yes, something went wrong with committing/pushing that to git. My
guess is that you didn't install from unstable and built the package
yourself. I'll fix it in git/salsa, but if you do "apt-get changelog
gamemode" you'll see the version in unstable has the change.

-Jonathan

-- 
  ⢀⣴⠾⠻⢶⣦⠀  Jonathan Carter (highvoltage) 
  ⣾⠁⢠⠒⠀⣿⡁  Debian Developer - https://wiki.debian.org/highvoltage
  ⢿⡄⠘⠷⠚⠋   https://debian.org | https://jonathancarter.org
  ⠈⠳⣄  Be Bold. Be brave. Debian has got your back.

Bug#853827: tracker-extract: Could not insert metadata for item

[Mike Paul]

Package: tracker-extract
Version: 2.1.6-1
Followup-For: Bug #853827

This happens to me as well, and it fills up my /var partition with endless
syslog errors from repeatedly trying to index .ogg files.  My /var/log/messages
is full of lines like:

Aug  6 00:33:50 magus tracker-extract[27409]: Could not insert metadata for
item
"file:///home/mike/Music/CD%20Rips/Katamari%20Fortissimo%20Damacy/Katamari%20Fortissimo%20Damacy%20-%2006%20-%20Lonely%20Rolling%20Star.ogg":
Subject `urn:uuid:9b074666-3f45-0909-ecb8-df6ace3a4f83' is not in domain
`nie:DataObject' of property `nie:dataSource'
Aug  6 00:33:50 magus tracker-extract[27409]: If the error above is recurrent
for the same item/ID, consider running "tracker-extract" in the terminal with
the TRACKER_VERBOSITY=3 environment variable, and filing a bug with the
additional information

...over and over for different files.  If I "tail -f" the log, I see screenfuls
of these messages go by very quickly, then it pauses for a few seconds, then
more screenfuls of the same messages.  The periods of log activity match the
"extracting metadata" activity shown by running "tracker daemon -f".

Running "TRACKER_VERBOSITY=3 tracker extract" on the file identified in the
message above, it shows:

---

** Message: 00:38:09.722: Starting tracker-extract 2.1.6
** Message: 00:38:09.722: General options:
** Message: 00:38:09.722:   Verbosity    0
** Message: 00:38:09.722:   Sched Idle  ...  1
** Message: 00:38:09.722:   Max bytes (per file)  .  1048576
Setting scheduler policy to SCHED_IDLE
Setting priority nice level to 19
Loading extractor rules... (/usr/share/tracker-miners/extract-rules)
  Loaded rule '10-abw.rule'
  Loaded rule '10-bmp.rule'
  Loaded rule '10-comics.rule'
  Loaded rule '10-dvi.rule'
  Loaded rule '10-ebooks.rule'
  Loaded rule '10-epub.rule'
  Loaded rule '10-flac.rule'
  Loaded rule '10-gif.rule'
  Loaded rule '10-html.rule'
  Loaded rule '10-ico.rule'
  Loaded rule '10-jpeg.rule'
  Loaded rule '10-mp3.rule'
  Loaded rule '10-msoffice.rule'
  Loaded rule '10-oasis.rule'
  Loaded rule '10-pdf.rule'
  Loaded rule '10-png.rule'
  Loaded rule '10-ps.rule'
  Loaded rule '10-raw.rule'
  Loaded rule '10-svg.rule'
  Loaded rule '10-tiff.rule'
  Loaded rule '10-vorbis.rule'
  Loaded rule '10-xmp.rule'
  Loaded rule '10-xps.rule'
  Loaded rule '11-iso.rule'
  Loaded rule '11-msoffice-xml.rule'
  Loaded rule '15-gstreamer-guess.rule'
  Loaded rule '15-playlist.rule'
  Loaded rule '15-source-code.rule'
  Loaded rule '90-gstreamer-audio-generic.rule'
  Loaded rule '90-gstreamer-image-generic.rule'
  Loaded rule '90-gstreamer-video-generic.rule'
  Loaded rule '90-text-generic.rule'
Extractor rules loaded
(tracker-extract:28911): dconf-DEBUG: 00:38:09.723: watch_established:
"/org/freedesktop/tracker/extract/" (establishing: 1)
MIME type guessed as 'audio/x-vorbis+ogg' (from GIO)
Using /usr/lib/x86_64-linux-gnu/tracker-miners-2.0/extract-modules/libextract-
vorbis.so...
@prefix rdf:  .
@prefix nmm:  .
@prefix nie:  .
@prefix nfo:  .

 nmm:artistName "Yohihito Yano" ;
  a nmm:Artist .

 nie:title
"Katamari Fortissimo Damacy" ;
  a nmm:MusicAlbum .


nmm:setNumber 1 ;
  nmm:albumDiscAlbum
 ;
  a nmm:MusicAlbumDisc .


nie:copyright "©Namco Ltd." ;
  nmm:trackNumber "6/21" ;
  nmm:performer  ;
  nfo:averageBitrate 160 ;
  nie:contentCreated "2005-05-18T00:00:00" ;
  nmm:musicAlbum 
;
  nmm:musicAlbumDisc  ;
  a nmm:MusicPiece , nfo:Audio ;
  nfo:duration 344 ;
  nie:title "Lonely Rolling Star" ;
  nie:license "All rights of the producer and of the owner of the work
reproduced reserved.  Unauthorized copying, public performance and broadcasting
of this record prohibited." .

---

I don't see any mention of the offending UUID from the error message.

These messages fill my /var partition within a day due to growth of
/var/log/messages, /var/log/syslog, and /var/log/user.log, which I think
qualifies as severity: critical.

Is there a way to disable this Tracker thing?  It seems to automatically and
silently (well, except the logspam) try to index all my files, which I neither
need nor want.  Disabling the "Files" toggle in the "Search" section of GNOME
Settings did not stop it.  Neither did disabling GNOME's search entirely.



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

Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: 

Bug#933997: gamemode isn't automatically activated for rise of the tomb raider

[Axel Regnat]

On Mon, 5 Aug 2019 23:07:24 +0200 Jonathan Carter 
 wrote:

> On 2019/08/05 22:36, Axel R. wrote:
> > Rise of the Tomb Raider is one of the few games which should 
automatically activate gamemode. But if I start the game through steam 
gamemoded -s says that gamemode is inactive. If I set the launchoption 
"gamemoderun %command%" gamemoded -s reports that gamemode is active.

>
> Ah yes, I can see why that happens, re-enabling the daemon in
> gamemode_1.4+git20190722.4ecac89-2 - which should hit unstable in a few
> hours.
>
> -Jonathan
>
>

Hi Jonathan,

Thanks for your fast response. I updated gamemode, libgamemode0 and 
libgamemodeauto0 to 1.4+git20190722.4ecac89-2 but that didn't change 
anything. I still need to set the launch option. I'm not experienced 
with git or salsa but I'm also unable to see any change there beside 
that you pushed new tags. Shouldn't there be a commit to re-enabling the 
daemon?


Axel

Bug#933622: formiko: ampersand escaping issues: Error on line 1: Entity did not end with a semicolon

[Ondřej Tůma]

Yes, it works by docutils writer.  Generated html are correct. 


problem was only the & character without amp; and gtk pango markup machine.




You can try it ;)




Ondra
--
Ondřej Tůma 
https://ipv6.mcbig.cz https://keybase.io/mcbig twitter: mcbig_cz

-- Původní e-mail --
Od: Paul Wise 
Komu: Ondřej Tůma , 933...@bugs.debian.org
Datum: 6. 8. 2019 3:33:14
Předmět: Bug#933622: formiko: ampersand escaping issues: Error on line 1:
Entity did not end with a semicolon
"Control: tags -1 + fixed-upstream
Control: forwarded -1 https://github.com/ondratu/formiko/commit/64b69b
552439009c8391744e55657642c2e7469a

On Mon, 2019-08-05 at 20:58 +0200, Ondřej Tůma wrote:

> bug is fixed in upstream git, and will be fixed in debian with new
> version.

I'm not sure that the commit linked above is the correct fix, instead
the markdown to HTML converter should be generating correct HTML.

In addition, the ampersand isn't the only character that needs to be
escaped when converting text to HTML:

* " is replaced with 
* & is replaced with 
* < is replaced with 
* > is replaced with 

--
bye,
pabs

https://wiki.debian.org/PaulWise



"

Bug#931414: ntpsec-ntpdate: if-up script fails to sync time

[Richard Laager]

On 7/4/19 5:21 AM, Masahiro Honda wrote:
> Here is a patch.

Thanks for the bug report and the patch!

> --- ntpsec-ntpdate.orig   2019-02-14 11:30:00.88213 +
> +++ ntpsec-ntpdate2019-07-04 09:35:51.210653439 +0100
> @@ -31,11 +31,12 @@
>  fi
>  
>  service="ntpsec"
> +export service

This looks to be the critical fix. I will merge this change.

>  invoke-rc.d --quiet "$service" stop >/dev/null 2>&1 || true
>  
>  # Avoid running more than one at a time
> -flock -n /run/lock/ntpsec-ntpdate /usr/sbin/ntpdate-debian -s $OPTS 
> 2>/dev/null || :
> +flock -n /run/lock/ntpsec-ntpdate /usr/sbin/ntpdate-debian $OPTS 2>/dev/null 
> | logger -t ntpsec-ntpdate || :

This change does two things. It removes -s from flock and it adds logging.

The -s seems to allow multiple ntpdate-debian processes to run
simultaneously, which seems bad. It seems like a correct change to
remove that, though it makes me wonder why it was there in the first
place. (This code was inherited from the ntp package.)

Are you getting interesting logging when ntpdate-debian runs?

-- 
Richard

Bug#934013: boost-defaults: Boost license file is not found

[Ryo IGARASHI]

Source: boost-defaults
Version: 1.67.0.1
Severity: serious
Justification: Policy 4.5

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear Maintainer,

Every boost packages, libboost*, contains debian/copyright file
which says:

```
copyright & license for Boost-Defaults for Debian.
The license for Boost itself may be found in file
/usr/share/doc/libboost-doc/HTML/LICENSE_1_0.txt
```

However, even if I installed libboost-doc package, the above path does
not exist at all. I cannot find the license for Boost itself.

I believe that the license for Boost itself should
also be available when only one e.g. libboost-test1.67 package is
installed.

P.S. I know that The license for the original Boost is the same as the
license for Boost-Defaults for Debian so that editing the wording might
be enough.

Best regards,
- -- 
Ryo IGARASHI, Ph.D.
rigar...@gmail.com

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

Kernel: Linux 4.4.0-17763-Microsoft
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8), 
LANGUAGE=ja_JP.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

-BEGIN PGP SIGNATURE-

iIkEARYKADEWIQSQVQWnJ6dEuIxNmESAtgFFC/hXNwUCXUj3WBMccmlnYXJhc2hA
Z21haWwuY29tAAoJEIC2AUUL+Fc35goA/1QXwA5BjOmWINst3Izx7Gv7k4KcTB/6
hR5Kqd3SiIS4AP9UjY3TWHdGVXZmDdk/5ZvD0s/kLMrdLBvvuolyxe44Dg==
=7nMT
-END PGP SIGNATURE-

Bug#934012: O: wand -- Python interface for ImageMagick library

[Changwoo Ryu]

Package: wnpp
Severity: normal

I orphan this package, wand.  I don't use it anymore.

I updated it recently (0.5.5-1) and it's in pretty good shape.

See https://salsa.debian.org/debian/wand if you are interested.

Bug#927829: goldencheetah: Strava sync seems impossible due to unsettable client secrets

[Satoru KURASHIKI]

hi,

On Wed, Apr 24, 2019 at 5:42 AM Matthew Sackman  wrote:
> When trying to authorise to my Strava account, I'm getting an "Host requires 
> authentication (204)" error back from Strava. This suggests, after some 
> searching, that this build is not being done with the registered client id in 
> Strava. I can completely understand this given Debian policies, and the fact 
> this is a DEV build. But, I've got a Strava "My API Application" created, and 
> have a suitable client id and secret, but I can't find any way of setting 
> this in Golden Cheetah. I see from the Golden Cheetah docs that these appear 
> to be a compile-time constants, which is a problem - I'm amazed I can't set 
> it in some configuration file. Without this, this package doesn't seem to be 
> able to work for me - if I can't import several years of rides from Strava 
> without recompiling Golden Cheetah myself then this package is of limited 
> use. Is there no way by which these secrets can be set via configuration 
> files?

You seem to understand its situation.
If you need its secret to interact with such online services, you have
to use upstream package, or self compiled one...

regards,

Bug#918890: Uploaded now

[Scott Kitterman]

On Thu, 10 Jan 2019 11:19:01 + Simon McVittie  wrote:
> Source: pyyaml
> Severity: wishlist
> 
> pyyaml 4.1 is available.
> 
> This version addresses CVE-2017-18342 (

Uploaded 5.1.2-1.

Scott K

Bug#919634: IP address blocked by wiki

[Paul Wise]

On Tue, Aug 6, 2019 at 4:33 AM Thiago Andrade Marques wrote:

> My ip 177.8.84.3 is locked to the Debian Wiki.
> Forbiden 403
>
> Would it be possible to unlock it?

Since this was blocked 2 years ago and not seen until recently, I've
unblocked it.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

Bug#933916: additional information

[Michael Stroucken]

When the problem occurs, iostat -xk shows the following:
avg-cpu:  %user   %nice %system %iowait  %steal   %idle
   0.000.000.25   24.940.00   74.81

Device: rrqm/s   wrqm/s r/s w/srkB/swkB/s
avgrq-sz avgqu-sz   await r_await w_await  svctm  %util
vda   0.00 0.000.000.00 0.00 0.00
0.00 0.000.000.000.00   0.00   0.00
vdb   0.00 0.000.000.00 0.00 0.00
0.00 1.000.000.000.00   0.00 100.00

Backtrace from all threads on the qemu process:
(gdb) thread apply all bt

Thread 7 (Thread 0x7f25e65ff700 (LWP 4428)):
#0  0x7f25ff2ba17f in pthread_cond_wait@@GLIBC_2.3.2 ()
   from /lib/x86_64-linux-gnu/libpthread.so.0
#1  0x560da8d5b359 in qemu_cond_wait ()
#2  0x560da8cadd0b in ?? ()
#3  0x560da8cae258 in ?? ()
#4  0x7f25ff2b44a4 in start_thread ()
   from /lib/x86_64-linux-gnu/libpthread.so.0
#5  0x7f25feff6d0f in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 6 (Thread 0x7f25e7fff700 (LWP 4426)):
#0  0x7f25fefef017 in ioctl () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x560da8a0a4b7 in kvm_vcpu_ioctl ()
#2  0x560da8a0a610 in kvm_cpu_exec ()
#3  0x560da89f8138 in ?? ()
#4  0x7f25ff2b44a4 in start_thread ()
   from /lib/x86_64-linux-gnu/libpthread.so.0
#5  0x7f25feff6d0f in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 5 (Thread 0x7f25f4a2c700 (LWP 4425)):
#0  0x7f25fefef017 in ioctl () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x560da8a0a4b7 in kvm_vcpu_ioctl ()
#2  0x560da8a0a610 in kvm_cpu_exec ()
#3  0x560da89f8138 in ?? ()
#4  0x7f25ff2b44a4 in start_thread ()
   from /lib/x86_64-linux-gnu/libpthread.so.0
#5  0x7f25feff6d0f in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 4 (Thread 0x7f25f522d700 (LWP 4424)):
#0  0x7f25fefef017 in ioctl () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x560da8a0a4b7 in kvm_vcpu_ioctl ()
#2  0x560da8a0a610 in kvm_cpu_exec ()
#3  0x560da89f8138 in ?? ()
#4  0x7f25ff2b44a4 in start_thread ()
   from /lib/x86_64-linux-gnu/libpthread.so.0
#5  0x7f25feff6d0f in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 3 (Thread 0x7f25f5a2e700 (LWP 4423)):
#0  0x7f25fefef017 in ioctl () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x560da8a0a4b7 in kvm_vcpu_ioctl ()
#2  0x560da8a0a610 in kvm_cpu_exec ()
#3  0x560da89f8138 in ?? ()
#4  0x7f25ff2b44a4 in start_thread ()
   from /lib/x86_64-linux-gnu/libpthread.so.0
#5  0x7f25feff6d0f in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 2 (Thread 0x7f25f6c32700 (LWP 4387)):
#0  0x7f25feff2469 in syscall () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x560da8d5b668 in qemu_event_wait ()
#2  0x560da8d6a94e in ?? ()
#3  0x7f25ff2b44a4 in start_thread ()
   from /lib/x86_64-linux-gnu/libpthread.so.0
#4  0x7f25feff6d0f in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 1 (Thread 0x7f2604776c80 (LWP 4386)):
#0  0x7f25fefed981 in ppoll () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x560da8cbd359 in qemu_poll_ns ()
#2  0x560da8cbcd6a in main_loop_wait ()
#3  0x560da89be1ed in main ()

(gdb) info thread
  Id   Target Id Frame
* 1Thread 0x7f2604776c80 (LWP 4386) "GUEST" 0x7f25fefed981 in
ppoll ()
   from /lib/x86_64-linux-gnu/libc.so.6
  2Thread 0x7f25f6c32700 (LWP 4387) "qemu-system-x86"
0x7f25feff2469 in syscall () from /lib/x86_64-linux-gnu/libc.so.6
  3Thread 0x7f25f5a2e700 (LWP 4423) "GUEST" 0x7f25fefef017 in
ioctl ()
   from /lib/x86_64-linux-gnu/libc.so.6
  4Thread 0x7f25f522d700 (LWP 4424) "GUEST" 0x7f25fefef017 in
ioctl ()
   from /lib/x86_64-linux-gnu/libc.so.6
  5Thread 0x7f25f4a2c700 (LWP 4425) "GUEST" 0x7f25fefef017 in
ioctl ()
   from /lib/x86_64-linux-gnu/libc.so.6
  6Thread 0x7f25e7fff700 (LWP 4426) "GUEST" 0x7f25fefef017 in
ioctl ()
   from /lib/x86_64-linux-gnu/libc.so.6
  7Thread 0x7f25e65ff700 (LWP 4428) "GUEST" 0x7f25ff2ba17f in
pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0

Bug#934011: ansible-lint: 'man ansible-lint' shows different location of default rules.

[Ryo IGARASHI]

Package: ansible-lint
Version: 4.1.0+dfsg.1-1
Severity: minor
Tags: patch

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear Maintainer,

'man ansible-lint' shows default rules are available under
/usr/local/lib/python3.5/dist-packages/ansiblelint/rules
instead of
/usr/lib/python3/dist-packages/ansiblelint/rules
where 'dpkg -L ansible-lint' shows.

I attached the patch which fix this problem in asciidoc format
of the mapage.

Best regards,
- -- 
Ryo IGARASHI, Ph.D.
rigar...@gmail.com


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

Kernel: Linux 4.4.0-17763-Microsoft
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8), 
LANGUAGE=ja_JP.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages ansible-lint depends on:
ii  ansible  2.7.7+dfsg-1
ii  python3  3.7.3-1
ii  python3-ruamel.yaml  0.15.34-1+b1
ii  python3-six  1.12.0-1
ii  python3-yaml 3.13-2

ansible-lint recommends no packages.

ansible-lint suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iIkEARYKADEWIQSQVQWnJ6dEuIxNmESAtgFFC/hXNwUCXUjmtxMccmlnYXJhc2hA
Z21haWwuY29tAAoJEIC2AUUL+Fc3ZOYA/39AMqncxdmSmGAI2FkK2JTf4+lG9C/d
5vKpfMSMsxCPAPwLUh7s1g9r+xSzhBPKDoJsEjrJ8TwJ8ZwN3mUpMPVFDw==
=EuFj
-END PGP SIGNATURE-
--- debian/ansible-lint.1.asciidoc.in.old   2019-08-06 11:23:54.864907900 
+0900
+++ debian/ansible-lint.1.asciidoc.in   2019-08-06 11:24:29.103290500 +0900
@@ -63,12 +63,12 @@
 *-r* 'RULESDIR'::
 
 specify one or more rules directories using one or more *-r* arguments. Any 
*-r*
-flags override the default rules in 
'/usr/local/lib/python3.5/dist-packages/ansiblelint/rules,'
+flags override the default rules in 
'/usr/lib/python3/dist-packages/ansiblelint/rules,'
 unless *-R* is also used.
 
 *-R*::
 
-Use default rules in 
'/usr/local/lib/python3.5/dist-packages/ansiblelint/rules' in addition to any 
extra
+Use default rules in '/usr/lib/python3/dist-packages/ansiblelint/rules' in 
addition to any extra
 rules directories specified with *-r*. There is no need to specify this if no 
*-r* flags are used
 
 *-t* 'TAGS'::

Bug#934010: virtualbox-source: virualbox-source dosn't build with linux 5.3

[Elimar Riesebieter]

Package: virtualbox-source
Version: 6.0.10-dfsg-3
Severity: important

Building virtualbox-source 6.0.10-dfsg-3 on kernel 5.3-rc3 gives:

CC [M]  
/usr/src/modass/usr_src/modules/virtualbox/vboxnetflt/linux/VBoxNetFlt-linux.o¬
/usr/src/modass/usr_src/modules/virtualbox/vboxnetflt/linux/VBoxNetFlt-linux.c: 
In function ‘vboxNetFltLinuxSkBufToSG’:¬
/usr/src/modass/usr_src/modules/virtualbox/vboxnetflt/linux/VBoxNetFlt-linux.c:928:36:
 error: ‘skb_frag_t’ {aka ‘struct skb_frag_struct’} has no member named 
‘bv_len’¬
 pSG->aSegs[iSeg].cb = pFrag->bv_len;¬
^~¬
/usr/src/modass/usr_src/modules/virtualbox/vboxnetflt/linux/VBoxNetFlt-linux.c:929:66:
 error: ‘skb_frag_t’ {aka ‘struct skb_frag_struct’} has no member named 
‘bv_offset’; did you mean ‘page_offset’?¬
 pSG->aSegs[iSeg].pv = VBOX_SKB_KMAP_FRAG(pFrag) + pFrag->bv_offset;¬
  ^¬
  page_offset¬
/usr/src/modass/usr_src/modules/virtualbox/vboxnetflt/linux/VBoxNetFlt-linux.c:949:40:
 error: ‘skb_frag_t’ {aka ‘struct skb_frag_struct’} has no member named 
‘bv_len’¬
 pSG->aSegs[iSeg].cb = pFrag->bv_len;¬
^~¬
/usr/src/modass/usr_src/modules/virtualbox/vboxnetflt/linux/VBoxNetFlt-linux.c:950:70:
 error: ‘skb_frag_t’ {aka ‘struct skb_frag_struct’} has no member named 
‘bv_offset’; did you mean ‘page_offset’?¬
 pSG->aSegs[iSeg].pv = VBOX_SKB_KMAP_FRAG(pFrag) + 
pFrag->bv_offset;¬
  ^¬
  
page_offset¬


6.0.10-dfsg-2 build just fine.

Thanks
Elimar

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

Kernel: Linux 5.3.0-rc3-galadriel-lxtec-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), 
LANGUAGE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages virtualbox-source depends on:
ii  build-essential   12.6
ii  bzip2 1.0.6-9.2
pn  debhelper-compat  
ii  kbuild1:0.1.9998svn3296+dfsg-1
ii  module-assistant  0.11.10

Versions of packages virtualbox-source recommends:
ii  virtualbox  6.0.10-dfsg-3

virtualbox-source suggests no packages.

-- no debconf information

Bug#932598: Upgrade to buster fails with start-stop-daemon error

[Ron Murray]

On 7/30/19 4:14 PM, Andreas Beckmann wrote:
> Hi Ron,
>
> On 21/07/2019 05.42, Ron Murray wrote:
>> On upgrade to buster, sendmail upgrade failed with this message:
>>
>>> start-stop-daemon: matching only on non-root pidfile 
>>> /var/run/sendmail/mta/sendmail.pid is insecure
>> Some work with Google found Debian bug #922395, which, although not
>> for sendmail, pointed the way to the solution.
> I've just uploaded sendmail 8.15.2-13 to unstable, it would be great if
> you could test this s.t. I have a datapoint whether this fix should be
> applied to buster, too.
>
> Thanks
>
> Andreas

Thanks for the update. The same problem occurred when I upgraded to
8.15.2-13 on my two testing (bullseye) boxes. Deleting the
/var/run/sendmail/mta/sendmail.pid file and re-running aptitude fixed it.

Sadly, I wasn't smart enough to get the details on the file before I
deleted it. I'm not even certain why it was there: I would have thought
that shutting down sendmail before the upgrade should have deleted it.
Perhaps this was the problem all along.

After getting sendmail started, the file looks like this:

> -rw-r- 1 root  smmta  53 Aug  5 22:14 sendmail.pid

Thanks,


 ,Ron

-- 
Ron Murray 
PGP Fingerprint: 4D99 70E3 2317 334B 141E  7B63 12F7 E865 B5E2 E761




signature.asc
Description: OpenPGP digital signature

Bug#934009: RM: python-pytest-bdd [all] -- NBS; Python 2 module retired

[Scott Talbert]

Package: ftp.debian.org
Severity: normal

Bug#850916: xzgv FTCBFS: uses build architecture build tools (gcc, pkg-config)

[Theodore Y. Ts'o]

On Wed, Jan 11, 2017 at 09:27:26AM +0100, Helmut Grohne wrote:
> Source: xzgv
> Version: 0.9.1-4
> Tags: patch
> User: helm...@debian.org
> Usertags: rebootstrap
> 
> xzgv fails to cross build from source, because it uses build
> architecture build tools. Simply adding the host architecture triplet as
> a prefix to gcc and pkg-config fixes the cross build. Please consider
> applying the attached patch.

xzgv 0.9.2-2 has been uploaded, and it's been converted to use dh.
Can you verify whether or not the cross build problems are still
present with xzgv?  I *think* dh/debhelper should handle fixing CC
automatically, right?  I suppose we might need use special handling
for pkg-config?

Thanks,

- Ted

Bug#933248: RFS: assaultcube/1.2.0.2-1 [ITA] -- realistic first-person-shooter

[Carlos Donizete Froes]

Hi Tobias,

> At least assaultcube-data needs to go to non-free. The engine could go
> to contrib if everything required for it it is free software. 
> 
> I strongly suggest that you use keep old packaging scheme (two source
> packages, assaultcube and assaultcube-data)
> 
> I'm not sure at all if putting the data on a git repository would
> violate their license. (it is not unmodified distribution then)
> 
> Srry, I think I have to throw in towel for that package…
> Please seek advice from debian-legal.

I kept the old packaging scheme by separating 'assaultcube (contrib) [1]' and
'assaultcube-data (non-free) [2]' without violating copyright.

Please could you analyze my two packages. :)

[1] https://mentors.debian.net/package/assaultcube
[2] https://mentors.debian.net/package/assaultcube-data

Thanks!

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


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

Bug#934008: mlterm: Remove fonts-baekmuk from Suggests

[Changwoo Ryu]

Package: mlterm
Version: 3.8.8-2
Severity: minor

Hello,

Please remove fonts-baekmuk from Suggests. The baekmuk fonts are old and lead
to undesirable result in modern displays.

I skimmed mlterm source code and I found no direct reference to the Baekmuk
fonts. So it seems that fonts-baekmuk is suggested as one Korean font.
Then I suggest to use fonts-noto-cjk | fonts-nanum instead.



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

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

Versions of packages mlterm depends on:
ii  libc6   2.28-10
ii  libfreetype62.9.1-4
ii  libgdk-pixbuf2.0-0  2.38.1+dfsg-1
ii  libglib2.0-02.60.6-1
ii  libx11-62:1.6.7-1
ii  mlterm-common   3.8.8-2

Versions of packages mlterm recommends:
ii  mlterm-tools  3.8.8-2

Versions of packages mlterm suggests:
ii  fonts-arphic-bsmi00lp   2.10-17
ii  fonts-arphic-gbsn00lp   2.11-15
ii  fonts-baekmuk   2.2-13
ii  fonts-freefont-ttf  20120503-9
ii  fonts-ipaexfont-gothic [fonts-japanese-gothic]  00401-1
ii  fonts-ipafont-gothic [fonts-japanese-gothic]00303-18
ii  fonts-nanum 20180306-3
ii  fonts-vlgothic [fonts-japanese-gothic]  20141206-5
pn  mlterm-im-m17nlib   
pn  mlterm-im-scim  
pn  mlterm-im-uim   
pn  t1-cyrillic 
pn  unifont 
pn  xfonts-efont-unicode

Bug#934007: stress-ng: Please, upload source-only to enter in testing

[Joao Eriberto Mota Filho]

Package: stress-ng
Version: 0.10.00-1
Severity: important

Dear maintainer,

Currently, only packages uploaded without binaries (debuild -S) will arrive
to testing. See more details here[1]. Please, re-upload your package.

[1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html

Regards,

Eriberto

Bug#933622: formiko: ampersand escaping issues: Error on line 1: Entity did not end with a semicolon

[Paul Wise]

Control: tags -1 + fixed-upstream
Control: forwarded -1 
https://github.com/ondratu/formiko/commit/64b69b552439009c8391744e55657642c2e7469a

On Mon, 2019-08-05 at 20:58 +0200, Ondřej Tůma wrote:

> bug is fixed in upstream git, and will be fixed in debian with new
> version.

I'm not sure that the commit linked above is the correct fix, instead
the markdown to HTML converter should be generating correct HTML.

In addition, the ampersand isn't the only character that needs to be
escaped when converting text to HTML:

 * " is replaced with 
 * & is replaced with 
 * < is replaced with 
 * > is replaced with 

-- 
bye,
pabs

https://wiki.debian.org/PaulWise





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

Bug#934006: mlterm: Menu contains ancient XIMs

[Changwoo Ryu]

Package: mlterm
Version: 3.8.8-2
Severity: normal

In debian/config-menu,

"XIM" {
"kinput2"   "xim=kinput2:ja_JP.eucJP"
"ami"   "xim=Ami:ko_KR.eucKR"
"xcin (big5)"   "xim=xcin:zh_TW.Big5"
"xcin (gb)" "xim=zh_CN.GB2312:zh_CN.GB2312"
"skkinput"  "xim=skkinput:ja_JP.eucJP"
}


These old input methods have been out of major use for more than a decade and
AFAIK are not in Debian anymore. mlterm-im-{fcitx,ibus,uim} plugin packages do
the job so this Debian specific menu is not needed.



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

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

Versions of packages mlterm depends on:
ii  libc6   2.28-10
ii  libfreetype62.9.1-4
ii  libgdk-pixbuf2.0-0  2.38.1+dfsg-1
ii  libglib2.0-02.60.6-1
ii  libx11-62:1.6.7-1
ii  mlterm-common   3.8.8-2

Versions of packages mlterm recommends:
ii  mlterm-tools  3.8.8-2

Versions of packages mlterm suggests:
ii  fonts-arphic-bsmi00lp   2.10-17
ii  fonts-arphic-gbsn00lp   2.11-15
ii  fonts-baekmuk   2.2-13
ii  fonts-freefont-ttf  20120503-9
ii  fonts-ipaexfont-gothic [fonts-japanese-gothic]  00401-1
ii  fonts-ipafont-gothic [fonts-japanese-gothic]00303-18
ii  fonts-nanum 20180306-3
ii  fonts-vlgothic [fonts-japanese-gothic]  20141206-5
pn  mlterm-im-m17nlib   
pn  mlterm-im-scim  
pn  mlterm-im-uim   
pn  t1-cyrillic 
pn  unifont 
pn  xfonts-efont-unicode

Bug#907425: Possible fix

[Felix Lechner]

Control: tag -1 + pending

Hi,

> Not sure of the cause but I note that matlab-gdf is
> "Section: contrib/science".

This MR tries to escape the forward slash in commands/reporting-html-reports.pm:

https://salsa.debian.org/lintian/lintian/merge_requests/241

The modified routine 'html_quote' is used here:


https://salsa.debian.org/lintian/lintian/blob/master/commands/reporting-html-reports.pm#L1062

The proposed fix is untested.

Kind regards,
Felix

diff --git a/commands/reporting-html-reports.pm
b/commands/reporting-html-reports.pm
index aed7a6b39..43911fae2 100644
--- a/commands/reporting-html-reports.pm
+++ b/commands/reporting-html-reports.pm
@@ -1128,6 +1128,9 @@ sub html_quote {
 if (index($text, '>') > -1) {
 $text =~ s/>/\/g;
 }
+if (index($text, '/') > -1) {
+$text =~ s/\//\/g;
+}
 return $text;
 }

Bug#934005: version is 10.3.10

[Oliver Kurth]

Sorry, I used the wrong package version - it's 10.3.10-1.

Olover

Bug#926823: executable-not-elf-or-script should consider PE binaries

[Felix Lechner]

Hi Michael,

On Mon, Aug 5, 2019 at 3:23 PM Michael Biebl  wrote:
>
> Why is this a bug in systemd then?

Dunno. I did not file the bug. I just know it's not in Lintian. :)

> If ld creates those files with the executable bit set, it feels weird
> that we have to work around that by manually removing that bit again.

Is the bit required? With a view toward security, it seems
disadvantageous to grant execution privileges to files not intended to
run in Debian. I checked both the UEFI [1] and the systemd boot [2]
specs, but found nothing about the executable bit. I planned to unset
the bit locally until I realized my GRUB2 boot sequence may not use
those files.

Kind regards,
Felix

[1] https://uefi.org/sites/default/files/resources/UEFI_Spec_2_8_final.pdf
[2] https://systemd.io/BOOT_LOADER_SPECIFICATION

Bug#934005: guest OS is not reported correctly

[Oliver Kurth]

Package: open-vm-tools
Version: 2:10.3.5-8

During testing, we found this problem:

After install the open-vm-tools 10.3.10 by "apt-get install open-vm-tools" in 
Debian 10.0.0 on ESXi 6.7GA , the guestID and guestFullName are not correct.

---VM Tools Version---
# apt-get install open-vm-tools
# vmtoolsd -v
VMware Tools daemon, version 10.3.10.10540 (build-12406962)

---guestInfo in ESXi 6.7GA---
Guest information:

(vim.vm.GuestInfo) {
   toolsStatus = "toolsOk",
   toolsVersionStatus = "guestToolsUnmanaged",
   toolsVersionStatus2 = "guestToolsUnmanaged",
   toolsRunningStatus = "guestToolsRunning",
   toolsVersion = "10346",
   toolsInstallType = "guestToolsTypeOpenVMTools",
   toolsUpdateStatus = (vim.vm.GuestInfo.ToolsUpdateStatus) null,
   guestId = "other4xLinux64Guest",    } else if (strstr(distroLower, " 10")) {


There is a possible workaround with changing the code by putting these two 
lines into /etc/vmware-tools/tools.conf :

[guestosinfo]
short-name = debian10-64

Oliver

Bug#933921: src:python-tablib: Unsafe use of yaml.load()

[Joseph Herlant]

Hi,

Thanks Scott for the report.
Tomas: the repository in Openstack was archived long ago because it
was ported to https://salsa.debian.org/python-team/modules/python-tablib
The module is used by other packages than openstack (like
django-tables if I remember correctly), so could you please hold off
the removal request please?
If the repo in the openstack group bother you, you can drop it but
please don't drop tablib (at least not the python3 version).

Thanks,
Joseph

Bug#933667: sagemath: FTBFS in sid

[Martin von Gagern]

Build log from 
https://launchpad.net/ubuntu/+source/sagemath/8.6-6build1/+build/17348800
shows SIGSEGV in sage.libs.gap.util.initialize. That makes this a
duplicate of https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932367
I believe. Merge?

Bug#932367: GAP_Initialize signature changed

[Martin von Gagern]

Instead of fixing GAP by backporting an upstream commit, we might also
consider updating sagemath to include said commit. The first release
to contain that is 8.8. I started
https://salsa.debian.org/science-team/sagemath/merge_requests/12 in
the hope that it helps getting that upgrade off the ground.

Bug#933370: chrony won't start

[Vincent Blut]

Control: merge -1 883241
Control: reassign -1 systemd
Control: tags -1 - moreinfo

Dear systemd maintainers,

We have found out in #902026 that the use of “Conflicts=” does not 
prevent systemd-timesyncd and chrony to run at the same time, those two 
bug reports that I’m reassigning to systemd seem to also be related to 
the way the “Conflicts=” setting works.


What we currently have in Stretch and Buster is:
   - systemd-timesyncd runs by default unless another NTP daemon is 
 installed on the system through the use of the 
 “ConditionFileIsExecutable=” condition.


   - all the other implementations of the NTP protocol conflict with 
 systemd-timesyncd.


The current state of affairs seems to render both systemd-timesyncd and 
chrony becoming inactive on some systems.  Concerning systemd-timesyncd, 
this is not surprising as “ConditionFileIsExecutable=!/usr/sbin/chronyd” 
is obviously not met.
To make chrony active at startup on those systems, one has to either 
completely disable systemd-timesyncd or override chrony’s unit file to 
drop the “Conflicts=systemd-timesyncd.service” setting.


Thankfully there is some work done¹ upstream which may improve the 
situation.


¹ https://github.com/systemd/systemd/pull/13136

On Fri, Aug 02, 2019 at 09:59:59AM -0700, Ross Boylan wrote:

Removing systemd-timesyncd from chrony's Conflicts directive worked.
Some comments and details below, with more in the attached log.


Thank you for testing Ross.


>I did systemctl disable systemd-timesyncd and now chrony runs (and
>stays running) on startup.

Disabling systemd-timesyncd was guaranteed enough to succeed. That shows
that chrony is probably not at fault here. However, before merging this
bug report with #883241 and reassigning them to systemd, I would really
appreciate if you could check what’s happening by removing
systemd-timesyncd.service from the “Conflicts=” line in the chrony unit
file.

Note that I would totally understand that you refuse to run some tests
again! I certainly do not want to burden you.

If you accept to run these tests, then:

# Reenable systemd-timesyncd
# systemctl enable systemd-timesyncd.service

# Edit chrony’s unit file
# systemctl edit --full chrony.service

That will invoke an editor. From there, remove
“systemd-timesyncd.service” from the “Conflicts=” line. Save & exit!


I did this, also inserting the
  Wants=time-sync.target
  Before=time-sync.target
directives into the new file.  I left the override file that has those
directives too; not sure if it gets checked if I've overridden the
whole file.


It does. Look for the “Drop-In:” line when running:
$ systemctl status chrony.service

Alternatively, you can get a list of *.conf files in drop-in directories 
by running:

$ systemd-delta --type extended


# Restart the system and report chrony’s status here (ditto for
systemd-timesyncd)


See attached, which was done with systemd.log_type=debug.  It also
gives the contents of the configuration files.

It worked properly: chrony was active on startup.


Thanks again!


Ross


Cheers,
Vincent


signature.asc
Description: PGP signature

Bug#923377: (No Subject)

[kwip000]

I have been having this same problem except on a separate partition ( not root).
I was able to get past the "failed to mount" issue by running modprobe but then 
I get

● zfs-share.service - ZFS file system shares
   Loaded: loaded (/lib/systemd/system/zfs-share.service; enabled; vendor 
preset: enabled)
   Active: failed (Result: exit-code) since Mon 2019-08-05 18:43:16 EDT; 9ms ago
 Docs: man:zfs(8)
  Process: 27806 ExecStartPre=/bin/rm -f /etc/dfs/sharetab (code=exited, 
status=0/SUCCESS)
  Process: 27807 ExecStart=/sbin/zfs share -a (code=exited, status=1/FAILURE)
Main PID: 27807 (code=exited, status=1/FAILURE)

Aug 05 18:43:16 X470-AORUS-ULTRA systemd[1]: Starting ZFS file system shares...
Aug 05 18:43:16 X470-AORUS-ULTRA zfs[27807]: cannot share 'Media': share(1M) 
failed
Aug 05 18:43:16 X470-AORUS-ULTRA systemd[1]: zfs-share.service: Main process 
exited, code=exited, status=1/FAILURE
Aug 05 18:43:16 X470-AORUS-ULTRA systemd[1]: zfs-share.service: Failed with 
result 'exit-code'.
Aug 05 18:43:16 X470-AORUS-ULTRA systemd[1]: Failed to start ZFS file system 
shares.
dpkg: error processing package zfsutils-linux (--configure):
installed zfsutils-linux package post-installation script subprocess returned 
error exit status 1
Setting up gcc-8-base:i386 (8.3.0-6) ...
Setting up libgpg-error-l10n (1.35-1) ...
dpkg: dependency problems prevent configuration of zfs-zed:
zfs-zed depends on zfsutils-linux (>= 0.7.12-2+deb10u1); however:
  Package zfsutils-linux is not configured yet.

dpkg: error processing package zfs-zed (--configure):
dependency problems - leaving unconfigured

I assumed it was my fault, something stupid I did, untill yesterday after a 
fresh install of buster, using ext4 for my root partition.

Sent with [ProtonMail](https://protonmail.com) Secure Email.

Bug#237470: (no subject)

[Miguel Figueiredo]

Could not reproduce on Debian stable (buster) and unstable with:

  apt-get --reinstall install systemd-sysv systemd
  apt-get --reinstall install coreutils debianutils

Currently, both are using apt 1.8.2.

--
Best regards / Melhores cumprimentos,

Miguel Figueiredo

Bug#930631: Wrong package reported.

[Kenyon Ralph]

On 2019-08-05T22:44:40+0100, Dai Trying  wrote:
> This "bug" is actually with xserver-xorg-core package and is caused by the
> modesetting DDX driver, can this be changed here or do I need to file a new
> bug report?

You can reassign the bug report:
https://www.debian.org/Bugs/server-control#reassign

(I also had basically this same problem when upgrading to buster with
my system which uses an Intel i915 graphics controller, and your
report helped me figure out that creating a new xorg.conf fixes it, so
thanks for that.)

-- 
Kenyon Ralph


signature.asc
Description: PGP signature

Bug#933967: Predictable interface names results in forced deauth of certain usb wifi adapters

[Michael Biebl]

Control: tags -1 + moreinfo

Am 05.08.19 um 17:32 schrieb Kathryn Tolsen:
> package: systemd

Which version is this?

> I had first observed this issue with Stretch and my Netgear WG111v3
> (RTL8168B chipset) using the rtl8168 driver over a year ago, and had a
> rough time running down the culprit and had discovered that disabling
> predictable ifnames with net.ifnames=0 resolved the issue.
> 
> Last night in #debian on freenode, a user came in with issues with a
> completely different device using a different driver and the problem had
> seemed familiar, and I recommended disabling the predictable ifnames,
> and it resolved their issue as well.
> 
> Information from this recent issue on Buster is as follows:
> 
> lsusb:
> Bus 001 Device 008: ID 148f:5372 Ralink Technology, Corp. RT5372
> Wireless Adapter
> 
> dmesg:
> ieee80211 phy1: rt2x00lib_request_firmware: Info - Loading firmware file
> 'rt2870.bin'
> rt2800usb 1-1:1.0: firmware: direct-loading firmware rt2870.bin
> ieee80211 phy1: rt2x00lib_request_firmware: Info - Firmware detected -
> version: 0.36
> 
> usb 1-1: new high-speed USB device number 8 using xhci_hcd
> usb 1-1: New USB device found, idVendor=148f, idProduct=5372, bcdDevice=
> 1.01
> usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
> usb 1-1: Product: 802.11 n WLAN
> usb 1-1: Manufacturer: Ralink
> 
> wlx9cefd5fdf30b: authenticate with 90:4c:81:01:76:00
> wlx9cefd5fdf30b: send auth to 90:4c:81:01:76:00 (try 1/3)
> wlx9cefd5fdf30b: authenticated
> wlx9cefd5fdf30b: authenticate with 90:4c:81:01:76:00
> wlx9cefd5fdf30b: send auth to 90:4c:81:01:76:00 (try 1/3)
> wlx9cefd5fdf30b: authenticated
> wlx9cefd5fdf30b: authenticate with 90:4c:81:01:76:00
> wlx9cefd5fdf30b: send auth to 90:4c:81:01:76:00 (try 1/3)
> wlx9cefd5fdf30b: authenticated
> wlx9cefd5fdf30b: aborting authentication with 90:4c:81:01:76:00 by local
> choice (Reason: 3=DEAUTH_LEAVING)
> IPv6: ADDRCONF(NETDEV_UP): wlx9cefd5fdf30b: link is not ready
> IPv6: ADDRCONF(NETDEV_UP): wlx9cefd5fdf30b: link is not ready
> 
> I am not sure where the problem lies.. in the kernel, firmware, systemd,
> udev.. idk.. but I'd had the same symptoms before with the Netgear
> adapter and rtl8168 where it would list APs attempt to connect,
> authenticate then forcibly deauth citing Reason 3, DEAUTH_LEAVING and
> say the link was not ready.. 
> 
> I had spent hours trying to figure it out when I came across an obscure
> post online that suggested it was a firmware bug related to predictable
> ifnames, and after disabling them and that resolving my issue I had
> ignored it as an obscure bug not likely to affect many users. 
> 
> Now however I am realizing that whatever this issue is, its far more
> widespread than I thought and is possibly more central and less related
> to specific adapters. Since we are now using systemd/udev predictable
> ifnames by default I figured this was something we need to run down. 
> 
> If I can provide any more information on the subject, please let me know
> as I do still have the Netgear WG111v3 adapter that I know causes this
> issue.

I've never seen this issue before. This smells like a driver problem to me.
Is the problem the long interface name or the fact that the interface
has been renamed?

Could you create a file /etc/systemd/network/70-wifi.link containing:
[Match]
MACAddress=90:4c:81:01:76:00

[Link]
Name=wifi0


(run update-initramfs -u and reboot)
Is the problem still reproducible then?
What if you make the Name= longer bit by bit
wifi01, wifi012, wifi0123 etc.








-- 
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#926823: executable-not-elf-or-script should consider PE binaries

[Michael Biebl]

On Mon, 5 Aug 2019 05:32:51 -0700 Felix Lechner
 wrote:
> Hi,
> 
> On Thu, May 2, 2019 at 9:27 AM Chris Lamb  wrote:
> >
> > This begs the question; why cannot the systemd packaging remove the
> > executable bits from these files?
> 
> On my testing system post-buster, the executable bits are still set:
> 
> $ ls -ald /usr/lib/systemd/boot/efi/*
> -rwxr-xr-x 1 root root 59730 Jul 18 10:38
> /usr/lib/systemd/boot/efi/linuxx64.efi.stub
> -rwxr-xr-x 1 root root 91765 Jul 18 10:38
> /usr/lib/systemd/boot/efi/systemd-bootx64.efi
> 
> May I please assign this bug to package systemd?
> 

Why is this a bug in systemd then?
If ld creates those files with the executable bit set, it feels weird
that we have to work around that by manually removing that bit again.

-- 
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#929652: systemd: sshd processes are not put into the correct slice/scope

[Michael Biebl]

On Mon, 27 May 2019 21:03:03 + Simon Beirnaert
 wrote:
> Package: systemd
> Version: 232-25+deb9u11
> Severity: normal
> 
> Dear Maintainer,
> 
> 
> Systemd does not seem to consistently put sshd processes under the
> relevant user's slice. I have a user with 10925 sshd processes related
> to its sessions. 7552 of those are put under session scopes in the
> user's slice. 3372 are put under system.slice (ssh.service). The ones
> under the user slice are neatly grouped into session scopes whereas
> the ones under the system slice are not.
> 
> This is making it impossible to put accurate limits to the sshd
> processes, or the user's processes. I can set TasksMax, but that only
> has a value if the tasks are counted correctly.
> 
> If there's any more information needed to debug this, please let me
> know.

Thanks for filing this issue in the upstream bug tracker.
It would be great if you can follow-up there. Afaics Lennart had some
questions.

Regards,
Michael

-- 
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#933858: I do not understand

[Ramón García]

What is the intended purpose of sysadm_t?

If the root user logs in the console, the context is
unconfined_u:unconfined_r:unconfined_t. If some user sudo to root,
that might be allowed or not, but if allowed, shouldn't the session
have the same rights as a root session? Otherwise, what is expected
from sudo is broken.

The same reasoning for su: doing su to root may be allowed or not,
depending on the user. But if allowed, shouldn't the session have the
same unrestricted permissions as a root session?

I believed that the purpose of sysadm_u was to determinate what users
can su/sudo to root+unconfined_t.

Bug#934004: ITP: golang-starlark -- Interpreter for the Starlark configuration language

[Emanuel Krivoy]

Package: wnpp
Severity: wishlist
Owner: Emanuel Krivoy 

* Package name: golang-starlark
  Version : 0.0~git20190717.fc7a7f4-1
  Upstream Author : The Bazel Authors
* URL : https://github.com/google/starlark-go
* License : BSD-3-clause
  Programming Lang: Go
  Description : Interpreter for the Starlark configuration language

Starlark is a dialect of Python intended for use as a configuration language.
Like Python, it is an untyped dynamic language with high-level data types,
first-class functions with lexical scope, and garbage collection. Unlike
CPython, independent Starlark threads execute in parallel, so Starlark
workloads scale well on parallel machines. Starlark is a small and simple
language with a familiar and highly readable syntax. You can use it as an
expressive notation for structured data, defining functions to eliminate
repetition, or you can use it to add scripting capabilities to an existing
application.

A Starlark interpreter is typically embedded within a larger application, and
the application may define additional domain-specific functions and data types
beyond those provided by the core language

This library is a dependency of delve (github.com/go-delve/delve, ITP in
#932835). If possible I'd like this package to be co-mantained/sponsored by the
Go Team.

Bug#934003: RFP: rget -- download URLs and verify the contents against a publicly recorded cryptographic log

[Francois Marier]

Package: wnpp
Severity: wishlist

* Package name: rget
  Version : 0.0.7
  Upstream Author : Brandon Philips 
* URL : https://github.com/merklecounty/rget
* License : Apache-2
  Programming Lang: Go
  Description : download URLs and verify the contents against a publicly 
recorded cryptographic log

rget downloads URLs and verifies the contents against a publicly recorded
cryptographic log. The public log gives users of rget a number of useful
properties:

- Verifiability of a downloaded URL's contents being identical to what the
  rest of the world sees

- Searchability of recorded content changes of a URL

- Notifications to any interested party about changes to the URLs contents

In practice the way the system works is a URL owner will publish the
cryptographic digests at a URL adjacent to the content a rget user is
downloading. The rget tool will download the digest and verify this digest
appears in the Certificate Transparency log via a specially crafted DNS
name.

More information at 
https://merklecounty.substack.com/p/rget-a-secure-download-user-story

Bug#930631: Wrong package reported.

[Dai Trying]

This "bug" is actually with xserver-xorg-core package and is caused by the
modesetting DDX driver, can this be changed here or do I need to file a new
bug report?

Bug#934002: RFS: assaultcube-data/1.2.0.2.1-1 [ITA] -- data files and documentation for AssaultCube

[Carlos Donizete Froes]

Package: sponsorship-requests
Severity: normal

  Dear mentors,

  I am looking for a sponsor for my package "assaultcube-data"

 * Package name: assaultcube-data
   Version : 1.2.0.2.1-1
   Upstream Author : Rabid Viper Productions
 * URL : http://assault.cubers.net/
 * License : Other
   Section : non-free/games

  It builds those binary packages:

  assaultcube-data - data files and documentation for AssaultCube

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

  https://mentors.debian.net/package/assaultcube-data

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

  dget -x 
https://mentors.debian.net/debian/pool/non-free/a/assaultcube-data/assaultcube-data_1.2.0.2.1-1.dsc

  More information about assaultcube-data can be obtained from 
https://gitlab.com/coringao/assaultcube-data.

  Changes since the last upload:

  assaultcube-data (1.2.0.2.1-1) unstable; urgency=low

  * New upstream release.
  * debian/changelog: Corrected file containing white space.
  * debian/control:
+ Bumped Standards-Version to 4.4.0.
- Changed from 'debhelper' to 'debhelper-compat' in
  Build-Depends field and bumped level to 12.
+ Changed upstream Vcs-* URLs in salsa.d.g.
+ Long description organized.
  * debian/copyright licenses organized.
  * Removed files (outdated):
- d/compat.
- d/assaultcube-data.doc-base.
  * debian/assaultcube-data.install and debian/assaultcube-data.links reviewed.
  * debian/upstream: Included metadata and signature key.
  * debian/rules:
- Changed and removed get-orig-source and version checking.
  * debian/watch: Changed to personal git mirrored in upstream git.

  Regards,
   Carlos Donizete Froes [a.k.a coringao]

Bug#934001: RFS: assaultcube/1.2.0.2.1-1 [ITA] -- realistic first-person-shooter

[Carlos Donizete Froes]

Package: sponsorship-requests
Severity: normal

  Dear mentors,

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

 * Package name: assaultcube
   Version : 1.2.0.2.1-1
   Upstream Author : Rabid Viper Productions
 * URL : http://assault.cubers.net/
 * License : Zlib
   Section : contrib/games

  It builds those binary packages:

  assaultcube - realistic first-person-shooter

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

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

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

  dget -x 
https://mentors.debian.net/debian/pool/contrib/a/assaultcube/assaultcube_1.2.0.2.1-1.dsc

  More information about assaultcube can be obtained from 
https://gitlab.com/coringao/assaultcube.

  Changes since the last upload:

  assaultcube (1.2.0.2.1-1) unstable; urgency=medium

  * New upstream release. (Closes: #726355, #727026, #779617)
  * Removed files (outdated):
- d/assaultcube.dirs.
- d/assautcube.xpm.
- d/autoreconf.
- d/compat.
- d/patches.
- d/README.Debian.
- d/README.source.
  * debian/assaultcube.desktop: Updated '.desktop' application shortcut file.
  * debian/assaultcube.install: Updated directory paths.
  * debian/changelog: Corrected file containing white space.
  * debian/control:
+ Build-Depends: Libraries updated for SDL2.
+ Bumped Standards-Version to 4.4.0.
- Changed from 'debhelper' to 'debhelper-compat' in
  Build-Depends field and bumped level to 12.
+ Changed upstream Vcs-* URLs in salsa.d.g. (Closes: #900467)
+ Long description organized.
  * debian/copyright:
+ Organized copyright for each software license.
+ Format-uri: Changed unversioned copyright format uri.
+ Adding myself copyright in debian/*.
  * Added debian/assaultcube.docs
  * Added debian/clean
  * debian/rules:
- Changed and removed get-orig-source and version checking.
  * debian/scripts: Updated executable scripts.
  * debian/upstream: Included metadata and signature key.
  * debian/watch: Changed to personal git mirrored in upstream git.

  Regards,
   Carlos Donizete Froes [a.k.a coringao]

Bug#934000: calibre: ebook-viewer no longer opens markdown files

[Daniel Reichelt]

Package: calibre
Version: 3.46.0+dfsg-1~bpo10+1
Severity: important

Hi,

calibre/buster ran fine, since 3.46 entered buster-bpo, it crashes on opening 
markdown files:


-8<--
$ echo "# I'm a heading" > foo.md
$ ebook-viewer foo.md
-8<--


The main windows shown, blocked by a common, modal error dialog, providing this 
stack trace:

-8<--
calibre, version 3.46.0
ERROR: Could not open e-book: Failed to read book, foo.md click "Show Details" 
for more information

Traceback (most recent call last):
  File "/usr/lib/calibre/calibre/utils/ipc/simple_worker.py", line 290, in main
res = {'result':func(*args, **kwargs)}
  File "/usr/lib/calibre/calibre/ebooks/oeb/iterator/book.py", line 64, in 
extract_book
plumber.opts, plumber.input_fmt, log, {}, tdir)
  File "/usr/lib/calibre/calibre/customize/conversion.py", line 246, in __call__
log, accelerators)
  File "/usr/lib/calibre/calibre/ebooks/conversion/plugins/txt_input.py", line 
261, in convert
input_mi, html = convert_markdown_with_metadata(txt, extensions=[x.strip() 
for x in options.markdown_extensions.split(',') if x.strip()])
  File "/usr/lib/calibre/calibre/ebooks/txt/processor.py", line 148, in 
convert_markdown_with_metadata
md = create_markdown_object(extensions)
  File "/usr/lib/calibre/calibre/ebooks/txt/processor.py", line 114, in 
create_markdown_object
from markdown import Markdown
  File "/usr/lib/calibre/calibre/startup.py", line 69, in load_module
return import_module(fullname[len('calibre.ebooks.'):])
  File "/usr/lib/python2.7/importlib/__init__.py", line 37, in import_module
__import__(name)
ValueError: Empty module name
-8<--


The package list below is from my main machine (buster+bpo), however this also 
happens on an up-to-date sid vm.

Let me know if you need more information!


Thanks
Daniel


-- System Information:
Debian Release: 10.0
  APT prefers proposed-updates
  APT policy: (990, 'proposed-updates'), (990, 'stable'), (500, 
'unstable-debug'), (500, 'testing-debug'), (500, 'stable-debug'), (500, 
'oldstable-updates'), (500, 'oldstable-proposed-updates'), (500, 
'oldstable-debug'), (500, 'stable'), (500, 'oldstable'), (99, 'testing'), (98, 
'unstable'), (96, 'oldoldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/bash
Init: sysvinit (via /sbin/init)

Versions of packages calibre depends on:
ii  calibre-bin  3.46.0+dfsg-1~bpo10+1
ii  fonts-liberation 1:1.07.4-9
ii  imagemagick  8:6.9.10.23+dfsg-2.1
ii  imagemagick-6.q16 [imagemagick]  8:6.9.10.23+dfsg-2.1
ii  libjpeg-turbo-progs  1:1.5.2-2+b1
ii  libjs-coffeescript   1.12.8~dfsg-4
ii  libjs-mathjax2.7.4+dfsg-1
ii  optipng  0.7.7-1
ii  poppler-utils0.71.0-5
ii  python-apsw  3.24.0-r1-1
ii  python-bs4   4.7.1-1
ii  python-chardet   3.0.4-3
ii  python-cherrypy3 8.9.1-2
ii  python-css-parser1.0.4-1
ii  python-cssselect 1.0.3-1
ii  python-cssutils  1.0.2-2
ii  python-dateutil  2.7.3-3
ii  python-dbus  1.2.8-3
ii  python-feedparser5.2.1-1
ii  python-html5-parser  0.4.5-1
ii  python-html5lib  1.0.1-1
ii  python-lxml  4.3.2-1
ii  python-markdown  3.0.1-3
ii  python-mechanize 1:0.2.5-3
ii  python-msgpack   0.5.6-1+b1
ii  python-netifaces 0.10.4-1+b1
ii  python-pil   5.4.1-2
ii  python-pkg-resources 40.8.0-1
ii  python-pyparsing 2.2.0+dfsg1-2
ii  python-pyqt5 5.11.3+dfsg-1+b3
ii  python-pyqt5.qtsvg   5.11.3+dfsg-1+b3
ii  python-pyqt5.qtwebkit5.11.3+dfsg-1+b3
ii  python-regex 0.1.20190207-1
ii  python-routes2.4.1-1
ii  python2.72.7.16-2
ii  xdg-utils1.1.3-1

Versions of packages calibre recommends:
ii  python-dnspython  1.16.0-1

Versions of packages calibre suggests:
pn  python-unrardll  

-- no debconf information

Bug#933950: gamemode 1.4 uploaded to debian unstable

[Jonathan Carter]

On 2019/08/05 21:23, Yaroslav Halchenko wrote:
> so there is no tags at all :-/

I don't usually use tags for such small packages because they're not
useful to me, but if they're useful for anyone I'll add them, so I added
them for an update I just pushed to unstable.

-Jonathan

-- 
  ⢀⣴⠾⠻⢶⣦⠀  Jonathan Carter (highvoltage) 
  ⣾⠁⢠⠒⠀⣿⡁  Debian Developer - https://wiki.debian.org/highvoltage
  ⢿⡄⠘⠷⠚⠋   https://debian.org | https://jonathancarter.org
  ⠈⠳⣄  Be Bold. Be brave. Debian has got your back.

Bug#933876: freecad: Can't create a new file in FreeCAD in Debian 10 Gnome Edition

[Weiqiang]

Package: freecad
Followup-For: Bug #933876

I solve this problem by myself.

Open a terminal window,and type this command:

export SVGA_VGPU10=0

then click "enter" on the keyboard.

Now open the FreeCAD again.It works.

I just find that this problem only happens in VMware virtual machine.

Please help me label this bug report "Resolved".Thanks Debian team.



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

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

Versions of packages freecad depends on:
ii  freecad-python2  0.18~pre1+dfsg1-5

Versions of packages freecad recommends:
ii  calculix-ccx  2.11-1+b3
ii  graphviz  2.40.1-6

Versions of packages freecad suggests:
pn  freecad-doc 
pn  povray  
pn  python-collada  

-- no debconf information

Bug#933999: openssh-server: please provide a runscript for runit

[Lorenzo Puliti]

Package: openssh-server
Version: 1:8.0p1-4
Severity: wishlist
Tags: patch

Dear Maintainer,

here is a patch to add support for Runit initialization system.
While writing the runscript I took a look at both the old sysv script 
and systemd unit. The sysv script has two tests that I omitted in
the runscript 

> ( /usr/sbin/sshd -\? 2>&1 | grep -q OpenSSH ) 2>/dev/null || exit 0


>if [ ! -c /dev/null ]; then
> 

I'm not sure, are those still relevant?
Also, note that the 'since=1:8.0p1-5' option in the openssh-server.runit file 
should match the version that actually adds the runscript. 

the git patch is attached, and there is also a MR on salsa
https://salsa.debian.org/ssh-team/openssh/merge_requests/7

If you need more details please ask

Thanks,
Lorenzo


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

Kernel: Linux 4.19.0-3-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: runit (via /run/runit.stopit)

Versions of packages openssh-server depends on:
ii  adduser3.118
ii  debconf [debconf-2.0]  1.5.73
ii  dpkg   1.19.7
ii  libaudit1  1:2.8.5-2
ii  libc6  2.28-10
ii  libcom-err21.45.3-3
ii  libgssapi-krb5-2   1.17-6
ii  libkrb5-3  1.17-6
ii  libpam-modules 1.3.1-5
ii  libpam-runtime 1.3.1-5
ii  libpam0g   1.3.1-5
ii  libselinux12.9-2
ii  libssl1.1  1.1.1c-1
pn  libsystemd0
ii  libwrap0   7.6.q-28
ii  lsb-base   10.2019051400
ii  openssh-client 1:8.0p1-4
ii  openssh-sftp-server1:8.0p1-4
ii  procps 2:3.3.15-2
ii  runit-helper   2.8.13.2
ii  ucf3.0038+nmu1
ii  zlib1g 1:1.2.11.dfsg-1

Versions of packages openssh-server recommends:
ii  libpam-elogind-compat [libpam-systemd]  1.3
ii  ncurses-term6.1+20190713-2
ii  xauth   1:1.0.10-1

Versions of packages openssh-server suggests:
ii  lxqt-openssh-askpass [ssh-askpass]  0.14.1-1
pn  molly-guard 
pn  monkeysphere
pn  rssh
pn  ufw 

-- debconf information excluded
>From 8a2040f54e832dd589dbf0cb62ffaee28e6dee7a Mon Sep 17 00:00:00 2001
From: Lorenzo Puliti 
Date: Mon, 5 Aug 2019 20:24:41 +0200
Subject: [PATCH] Add a runscript for runit

Add a 'run' and a 'finish' script for runit init system;
rely on dh-runit for maintscript code.
---
 debian/control |  2 ++
 debian/openssh-server.runit|  1 +
 debian/openssh-server.ssh.runscript/finish | 16 
 debian/openssh-server.ssh.runscript/run| 20 
 debian/rules   |  2 +-
 5 files changed, 40 insertions(+), 1 deletion(-)
 create mode 100644 debian/openssh-server.runit
 create mode 100644 debian/openssh-server.ssh.runscript/finish
 create mode 100644 debian/openssh-server.ssh.runscript/run

diff --git a/debian/control b/debian/control
index c690df075..eab4e2b6e 100644
--- a/debian/control
+++ b/debian/control
@@ -19,6 +19,7 @@ Build-Depends: autotools-dev,
libwrap0-dev | libwrap-dev,
pkg-config,
zlib1g-dev (>= 1:1.2.3),
+   dh-runit(>=2.8.8),
 Standards-Version: 4.1.0
 Uploaders: Colin Watson ,
Matthew Vernon ,
@@ -92,6 +93,7 @@ Conflicts: sftp,
 Replaces: openssh-client (<< 1:7.9p1-8),
   ssh,
   ssh-krb5,
+Breaks: ${runit:Breaks}
 Suggests: molly-guard,
   monkeysphere,
   rssh,
diff --git a/debian/openssh-server.runit b/debian/openssh-server.runit
new file mode 100644
index 0..cb659a00b
--- /dev/null
+++ b/debian/openssh-server.runit
@@ -0,0 +1 @@
+debian/openssh-server.ssh.runscript logscript,name=ssh,since=1:8.0p1-5
diff --git a/debian/openssh-server.ssh.runscript/finish 
b/debian/openssh-server.ssh.runscript/finish
new file mode 100644
index 0..7e29ef1db
--- /dev/null
+++ b/debian/openssh-server.ssh.runscript/finish
@@ -0,0 +1,16 @@
+#!/bin/sh
+set -e
+
+NAME=ssh
+
+[ $1 = -1 ] && echo "runsv: ERROR in $NAME: unexpected error or wrong sh 
syntax"
+# no need to stop the service here, runsv will stop trying after the first 
attempt
+
+[ $1 = 161 ] && echo "runsv: ERROR $1 in $NAME: disabled by local settings" \
+ && sv d $(dirname $0) && exit 0
+
+[ $1 = 162 ] && echo "runsv: ERROR $1 in $NAME: configtest or early setup 
failed" \
+ && sv d $(dirname $0) && exit 0
+
+echo "$NAME Stopped"   
+
diff --git a/debian/openssh-server.ssh.runscript/run 
b/debian/openssh-server.ssh.runscript/run
new file mode 100644
index 

Bug#933997: gamemode isn't automatically activated for rise of the tomb raider

[Jonathan Carter]

On 2019/08/05 22:36, Axel R. wrote:
> Rise of the Tomb Raider is one of the few games which should automatically 
> activate gamemode. But if I start the game through steam gamemoded -s says 
> that gamemode is inactive. If I set the launchoption "gamemoderun %command%" 
> gamemoded -s reports that gamemode is active.

Ah yes, I can see why that happens, re-enabling the daemon in
gamemode_1.4+git20190722.4ecac89-2 - which should hit unstable in a few
hours.

-Jonathan

Bug#933997: gamemode isn't automatically activated for rise of the tomb raider

[at46]

Just saw that I forgot to update libgamemode0 and libgamemodeauto0. I 
did that now rebooted and tried again. Same result. I need to set 
gamemoderun %command% as launchoption or gamemode isn't active in RotTR.


Axel

Bug#912303: ITA: libopenhmd -- API and drivers for immersive

[Emmanuel Arias]

2019-08-05 17:03 GMT-03:00, Bálint Réczey :
> Hi Emmanuel,
>
> Emmanuel Arias  ezt írta (időpont: 2019.
> aug. 5., H, 21:43):
>>
>> Hi I am working on the new usptream version. You can see on salsa.
>>
>> I CC to Bálint to help to upload the package.
>>
>> Bálint do you prefer that send the package to mentors? or you can take
>> from salsa?
>
> I was happy to see that you already adopted the package, it just looks
> like the changelog entry was not formatted correctly to close this
> bug.

Yes, that was going to be my next question

> It is also an established practice to work with the same mentor who
> sponsor all the uploads and help improving by giving feedback on the
> packaging changes.
> I see Adam sponsored the previous upload thus he would be a more
> natural choice and I'm wondering if he would like to keep sponsoring
> uploads.
>
> Cheers,
> Balint
>
> PS: If Adam passes I can't safely promise ongoing sponsoring, but I
> can help out with occasional uploads.
>
>>
>> Regards
>>
>> --
>> Arias Emmanuel
>> http://eamanu.com
>> Github/Gitlab; @eamanu
>> Debian: @eamanu-guest
>

Cheers,
Emmanuel

Bug#933995: ITP: Mmg

[Mattia Rizzolo]

Control: reassign -1 wnpp

On Mon, Aug 05, 2019 at 10:16:43PM +0200, Nico Schlömer wrote:
> Package: mmg
> Version: 5.4.1-201908051833-1eoan1

ITPs are filed against the pseudo-package wnpp, not against a
non-existent package.

See https://debian.org/devel/wnpp/ for more details.

-- 
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#933997: gamemode isn't automatically activated for rise of the tomb raider

[Axel R.]

Package: gamemode
Version: 1.4+git20190722.4ecac89-1
Severity: normal

Dear Maintainer,

Rise of the Tomb Raider is one of the few games which should automatically 
activate gamemode. But if I start the game through steam gamemoded -s says that 
gamemode is inactive. If I set the launchoption "gamemoderun %command%" 
gamemoded -s reports that gamemode is active.

Axel




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

Kernel: Linux 5.2.3 (SMP w/12 CPU cores)
Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), 
LANGUAGE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gamemode depends on:
ii  init-system-helpers  1.57
ii  libc62.28-10
ii  libgamemode0 1.2-6
ii  libgamemodeauto0 1.2-6
ii  libsystemd0  241-7

gamemode recommends no packages.

gamemode suggests no packages.

-- no debconf information

Bug#933998: Please update nfs-utils

[Orion Poplawski]

Package: nfs-utils
Version: 1:1.3.4-2.5

nfs-utils 1.3.4 is over 3 years old at this point.  Please update to the
version 2 track, at least in your development releases.



smime.p7s
Description: S/MIME Cryptographic Signature

Bug#932438: RFS: irqbalance/1.6.0-1 [ITA] -- Daemon to balance interrupts for SMP systems

[Paride Legovini]

Dmitry Bogatov wrote on 23/07/2019:
> [2019-07-21 11:36] Paride Legovini 
>>> 1. In [942ed5e] you added this line:
>>>
>>> export DEB_LDFLAGS_MAINT_APPEND = -Wl,--as-needed
>>>
>>>Why is it needed? Maybe, these flags should be provided by
>>>dpkg-buildflags(1)?
>>
>> dpkg-buildflags does not currently provide the --as-needed flag to the
>> linker, see:
>>
>> https://wiki.debian.org/HardeningWalkthrough
>>
>> or just try. The flags are not needed but I think using them when
>> possible is good practice. For what --as-needed does see ld(1).
> 
> As I understand, this with this flag linker does not make dynamically
> linked binary depend on library, that was passed on command line, but
> none of its symbols is used.
> 
> If this is correct, question is why build system system links unused
> library in first place.

That's my understanding too. In this case I'm pretty sure the binaries
are not getting linked against extra libraries. Maybe in larger project
it could be helpful to have a final prune of eventual extra libs.

Do you suggest dropping those extra flags?

>>> 3. What is "irqbalance-ui"? It has no manpage, not referenced in
>>>irqbalance(1) and even after source diving I can't understand how to
>>>use it.
>>
>> I'll probably add a stub manpage for it.
> 
> Good.

Done, and I upstreamed it:

https://github.com/Irqbalance/irqbalance/commit/28575ddb46773a44

>>> 4. Situation with "oneshot" option is quite... inconvenient.
>>>
>>>* If you have ONESHOT option set, `/etc/init.d/irqbalance status`
>>>  will report failure. It can be fixed by checking for ONESHOT
>>>  variable in status) clause;

This is fixed now.

>>>* current runscript does not respect ONESHOT option. It can be fixed
>>>  with something like
>>>
>>>#!/bin/sh
>>>. /etc/default/irqbalance
>>>if [ -n "${ONESHOT:-}" ] ; then
>>>irqbalance --oneshot
>>>sv down irqbalance
>>>else
>>>exec irqbalance --foreground
>>>fi
>>>
>>>  but it would be quite unnatural. I think proper solution would be
>>>  separation of /etc/init.d/irqbalance and 
>>> /etc/init.d/irqbalance-oneshot.
>>
>> I agree calling `sv down` from the runscript is ugly, on the other side
>> I don't really like the idea of having two sets of init scripts for
>> three init systems. Moreover while dh_installsystemd and dh_installinit
>> have a --no-enable option, dh_unit does not, requiring some manual
>> (hacky) handling.
> 
> Runit does not have support for "one-shot" invocations by design: it is
> process supervisor, after all. But I agree, doubling number of initfiles
> for three init systems is considerable burden.
> 
> So please check for $ONESHOT in init.d script, I will provide patch for
> runscript after.

OK, thanks!

>>>  5. Do we really need debconf to configure oneshot feature? Debconf
>>> question block installation process, so they are not to be used
>>> lightly, imho. Even ssh server does not use debconf to make me
>>> review its config, which is of much more importance.
>>
>> I am more than happy with dropping it entirely.
> 
> Good.

Done; I hope the note in d/NEWS is clear enough.

The new commits are out for review:

https://salsa.debian.org/paride-guest/irqbalance

Thanks,

Paride

Bug#919634: IP address blocked by wiki

[Thiago Andrade Marques]

Package: wiki.debian.org
Followup-For: Bug #919634

Dear Maintainer,

My ip 177.8.84.3 is locked to the Debian Wiki.
Forbiden 403

Would it be possible to unlock it?

Regards.

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

Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), 
LANGUAGE=pt_BR:pt:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#927165: luks 2 in Buster

[Jack Feuerkogel]

Hello,

I just wanted to mention, that this situation of version-change, from 
luks 1 to luks 2, makes a multi-boot Stretch-Buster impossible - at 
least in my situation.

I had sda1 as /boot, sda2 as encrypted Stretch (luks 1), Grub in MBR and 
installed Buster (I used the XFCE4-installation-CD) encrypted (luks 2) 
to sda3 (all primary Partitions). Now the fact is, that I cannot start 
Stretch on sda2 anymore, not with the installed Grub, nor with any 
"Rescuedisks", or similar...

I had to chroot in Stretch, install Grub from there again and build the 
"initram.img" new, e.g. update it with "dpkg-reconfigure cryptsetup" 
afterwards - now I can start Stretch again, but not at all Buster...

Theres also a second bug about this: after installation of Buster, I can 
see "cryptsetup" as package installed, but I cannot fetch the command in 
a terminal (as root). Neighter "cryptsetup"-command, nor 
"dpkg-reconfigure"-command is available in terminal, even if the 
packages are shown as installed.

But if I use the XFCE4-installation-CD in "rescue/repair-mode" on sda3 
(Buster) as root, these commands are available again...

Greetings, Jack

Bug#933899: devscripts 2.19.5+deb10u1 flagged for acceptance

[Adam D Barratt]

Control: tags -1 + pending

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian buster.

Thanks for your contribution!

Upload details
==

Package: devscripts
Version: 2.19.5+deb10u1

Explanation: debchange: target buster-backports with --bpo

Bug#933996: brandy: CVE-2019-14665 CVE-2019-14663 CVE-2019-14662

[Salvatore Bonaccorso]

Source: brandy
Version: 1.20.1-1
Severity: important
Tags: security upstream

Hi,

The following vulnerabilities were published for brandy.

CVE-2019-14665[0]:
| Brandy 1.20.1 has a heap-based buffer overflow in define_array in
| variables.c via crafted BASIC source code.


CVE-2019-14663[1]:
| Brandy 1.20.1 has a stack-based buffer overflow in fileio_openin in
| fileio.c via crafted BASIC source code.


CVE-2019-14662[2]:
| Brandy 1.20.1 has a stack-based buffer overflow in fileio_openout in
| fileio.c via crafted BASIC source code.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2019-14665
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14665
[1] https://security-tracker.debian.org/tracker/CVE-2019-14663
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14663
[2] https://security-tracker.debian.org/tracker/CVE-2019-14662
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14662

Regards,
Salvatore

Bug#933995: ITP: Mmg

[Nico Schlömer]

Package: mmg
Version: 5.4.1-201908051833-1eoan1
Severity: wishlist

I intent to package Mmg [1], a (scientific) mesh generator and optimizer. It
produces pretty high-quality 3D meshes, is open-source and well-supported by
its GitHub upstream [2].

I'm working on this in a salsa repo [3].

Cheers,
Nico


[1] https://www.mmgtools.org
[2] https://github.com/MmgTools/mmg
[3] https://salsa.debian.org/science-team/mmg



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

Kernel: Linux 5.2.0-8-generic (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)
LSM: AppArmor: enabled

Versions of packages mmg depends on:
ii  libc6   2.29-0ubuntu3
ii  libmmg  5.4.1-201908051833-1eoan1

mmg recommends no packages.

mmg suggests no packages.

-- no debconf information

Bug#897926: Another voice to include this

[Andreas Kirbach]

It would be nice if this config option could be included for future builds.

It seems to be available since 1.11.5 according to
https://www.nginx.com/blog/nginx-dynamic-modules-how-they-work/#compatibility
and would make things quite a bit easier.

Thanks for your work!

-- 
Andreas Kirbach
Technischer Leiter

forumhome GmbH & Co. KG
Bruchstr. 54a
67098 Bad Dürkheim
Tel.: +49-6322-91 995-15
Fax:  +49-6322-91 995-19

akirb...@forumhome.com
www.forumhome.com

Sitz der Gesellschaft: Bad Dürkheim
Handelsregister: Ludwigshafen/ Rhein HRA 60968
USt-Id: DE 285 908 418
Persönlich haftende Gesellschafterin: OSV OnlineService Verwaltungs GmbH

OSV OnlineService-Verwaltungs GmbH
Sitz der Gesellschaft: Bad Dürkheim
Handelsregister: Ludwigshafen/ Rhein HRB 63178
Geschäftsführer: Carsten Grentrup

--
--
Forumhome sucht Praktikanten im Bereich Online-Marketing, Webdesign und
Webbasierte Softwareentwicklung!
Interesse? Informieren Sie sich unter
http://de.forumhome.com/content/10-jobs und schicken Sie uns Ihre
Bewerbungsunterlagen an j...@forumhome.com
Wir freuen uns auf Sie!
--
--

Diese E-Mail enthält vertrauliche oder rechtlich geschützte Informationen.
Wenn Sie nicht der beabsichtigte Empfänger oder dessen Vertreter sind,
informieren Sie bitte sofort den Absender und löschen Sie diese E-Mail.
Das unbefugte Kopieren dieser E-Mail oder die unbefugte Weitergabe der
enthaltenen Informationen ist nicht gestattet.

The information contained in this message is confidential or protected
by law. If you are not the intended recipient, please contact the sender
and delete this message.
Any unauthorised copying of this message or unauthorised distribution of
the information contained herein is prohibited.

---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus

Bug#872754: fetchmail: tls_process_server_hello:unsupported protocol

[Matthias Andree]

On Fri, 21 Jun 2019 11:44:28 +0200 Matthias Andree
 wrote:
> On Sat, 27 Oct 2018 20:16:17 +0200 Nicolas Boulenguez
>  wrote:
> > Package: fetchmail
> > Followup-For: Bug #872754
> >
> > Hello.
> > I have tried 6.4.0~beta4-1 in experimental.
> > This resulted in:
> >
> > reading message for *:1 among * flushed
> > (maybe unrelated) show_signal_msg: 1 callbacks suppressed
> > fetchmail: segfault at 14 ip 560d2f73a718 sp 7ffe8242c790
> error 6 in fetchmail[560d2f716000+44000]
> >
> > Feel free to contact me if you want to reproduce the issue.
>
> Nicolas,
>
> If you can reproduce the issue, please install debug symbols and get me
> a stack backtrace. Merci d'avance.
>
> Regards,
> Matthias

Nicolas,

can you reproduce this and get me a stack backtrace? I need to urge a
bit since I need to release 6.4.0 soonish and would want to fix a
crasher bug...

Merci.

Regards,
Matthias





signature.asc
Description: OpenPGP digital signature

Bug#912303: ITA: libopenhmd -- API and drivers for immersive

[Bálint Réczey]

Hi Emmanuel,

Emmanuel Arias  ezt írta (időpont: 2019.
aug. 5., H, 21:43):
>
> Hi I am working on the new usptream version. You can see on salsa.
>
> I CC to Bálint to help to upload the package.
>
> Bálint do you prefer that send the package to mentors? or you can take from 
> salsa?

I was happy to see that you already adopted the package, it just looks
like the changelog entry was not formatted correctly to close this
bug.
It is also an established practice to work with the same mentor who
sponsor all the uploads and help improving by giving feedback on the
packaging changes.
I see Adam sponsored the previous upload thus he would be a more
natural choice and I'm wondering if he would like to keep sponsoring
uploads.

Cheers,
Balint

PS: If Adam passes I can't safely promise ongoing sponsoring, but I
can help out with occasional uploads.

>
> Regards
>
> --
> Arias Emmanuel
> http://eamanu.com
> Github/Gitlab; @eamanu
> Debian: @eamanu-guest

Bug#933994: FTBFS because depends on lwt.syntax

[Stéphane Glondu]

Source: ocaml-sqlexpr
Version: 0.5.5-3
Severity: serious

Hello,

As lwt is a key package and because of [1], its camlp4 dependency has
been removed, removing lwt.syntax. Now, ocaml-sqlexpr FTBFS because it
depends on lwt.syntax.

Please provide an ocaml-usb package that does not depend on lwt.syntax
or, better, on camlp4.

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933722

Cheers,

-- 
Stéphane


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

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

Bug#933993: FTBFS because depends on lwt.syntax

[Stéphane Glondu]

Source: ocaml-usb
Version: 1.3.0-4
Severity: serious

Hello,

As lwt is a key package and because of [1], its camlp4 dependency has
been removed, removing lwt.syntax. Now, ocaml-usb FTBFS because it depends
on lwt.syntax.

Please provide an ocaml-usb package that does not depend on lwt.syntax or,
better, on camlp4.

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933722

Cheers,

-- 
Stéphane

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

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

Bug#933992: FTBFS without lwt.syntax

[Stéphane Glondu]

Source: obus
Version: 1.1.5-6
Severity: serious

Hello,

As lwt is a key package and because of [1], its camlp4 dependency has
been removed, removing lwt.syntax. Now, obus FTBFS because it depends
on lwt.syntax.

Please provide an obus package that does not depend on lwt.syntax or,
better, on camlp4.

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933722

Cheers,

-- 
Stéphane

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

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

Bug#933958: The golang FTBFS on amd64 should be fixed

[Dr. Tobias Quathamer]

control: reopen -1
control: reassign -1 src:golang-1.12
control: found -1 1.12.7-2

Am 05.08.19 um 20:59 schrieb Shengjing Zhu:
> Hi,
> 
> On Tue, Aug 6, 2019 at 2:03 AM Dr. Tobias Quathamer  wrote:
>>
>> the FTBFS of golang should be fixed. It was due to the GOCACHE changes
>> from Go 1.11 to Go 1.12. Anthony Fok has just fixed this in dh-golang.
>>
> 
> The golang compiler doesn't build depends dh-golang. So any change in
> dh-golang won't fix the compiler itself.

You're right, of course. I jumped to that conclusion due to the error
message "failed to initialize build cache".

I don't know why my first build succeeded -- now I can reproduce the
FTBFS :-(

However, I think I have found the solution for golang-1.12 (very similar
to dh-golang). I'm currently building the package and will upload the
fix soon.

Regards,
Tobias



signature.asc
Description: OpenPGP digital signature

Bug#933984: RM: pyramid-beaker/0.6.1+ds1-1 -- RoM; no Py3 and no revdeps

[Mattia Rizzolo]

Control: reassign -1 ftp.debian.org
Control: retitle -1 RM: pyramid-beaker -- RoM; No Python3 port and no rerverse 
dependencies


On Tue, Aug 06, 2019 at 12:11:54AM +0500, Andrey Rahmatullin wrote:
> Removal from unstable.

Removals from unstable are handled by ftp-master.  Reassigning.
(and also has a singly differnet format for the title)

-- 
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#933983: RM: storm/0.19-2 -- RoQA; orphaned; no Py3 and no revdeps

[Mattia Rizzolo]

Control: reassign -1 ftp.debian.org
Control: retitle -1 RM: storm -- RoQA; orphaned; no Python 3 port and no 
reverse dependencies

On Tue, Aug 06, 2019 at 12:11:15AM +0500, Andrey Rahmatullin wrote:
> > From which suite?
> From unstable please.

Reassigning accordingly.

-- 
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#933983: RM: storm/0.19-2 -- RoQA; orphaned; no Py3 and no revdeps

[Andrey Rahmatullin]

On Mon, Aug 05, 2019 at 07:39:54PM +0100, Adam D. Barratt wrote:
> > Package: release.debian.org
> > Severity: normal
> > User: release.debian@packages.debian.org
> > Usertags: rm
> > 
> > Orphaned, doesn't support Python 2, doesn't have revdeps (checked
> > with `dak rm
> > -Rn storm`).
> > 
> > No Py3 support upstream either: https://bugs.launchpad.net/storm/+bug
> > /1530734
> 
> From which suite?
From unstable please.

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Bug#933984: RM: pyramid-beaker/0.6.1+ds1-1 -- RoM; no Py3 and no revdeps

[Andrey Rahmatullin]

Removal from unstable.

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Bug#912303: ITA: libopenhmd -- API and drivers for immersive

[Emmanuel Arias]

Hi I am working on the new usptream version. You can see on salsa.

I CC to Bálint to help to upload the package.

Bálint do you prefer that send the package to mentors? or you can take from
salsa?

Regards

-- 
Arias Emmanuel
http://eamanu.com
Github/Gitlab; @eamanu
Debian: @eamanu-guest

Bug#933147: buster-pu: package libsdl2-image/2.0.4+dfsg1+deb10u1

[Salvatore Bonaccorso]

Hi Hugo,

On Mon, Aug 05, 2019 at 08:28:00AM +0200, Hugo Lefeuvre wrote:
> Hi Salvatore,
> 
> > Maybe I'm missing something but but please double check. Can it be
> > that the stretch-pu upload contains the fix
> > https://hg.libsdl.org/SDL_image/rev/b1a80aec2b10 for TALOS-2019-0842
> > but the buster-pu one missed it? (Note this has a new CVE assigned
> > CVE-2019-5058, the change afaics is included in your stretch-pu
> > debdiff, is this right? but not in the buster-pu one?)
> 
> Thanks for catching this. The situation is quite messy, so I will try to
> summarize it in a few words.
> 
> CVE-2018-3977 is the actual buffer overflow in IMG_pcx.c. This
> vulnerabilitity was "fixed" via [0], however the fix is broken (the check
> should be done for y, not ty). Talos decided to report the remaining issue
> as a separate vulnerability, TALOS-2019-0842, which was recently assigned
> CVE-2019-5058. It was fixed via [1].
> 
> CVE-2019-5058/TALOS-2019-0842 is not a new vulnerability, it's just
> CVE-2018-3977 which wasn't fixed properly.

Ack, thanks for summarizing the situation.

> Buster received [0] per 2.0.4+dfsg1-1, but not [1]. Even if I was aware
> that the initial patch was broken (see stretch patch descriptions), I
> failed to handle this properly in the buster version.
> 
> As far as I remember, I did not upload this diff yet. I'll just provide an
> updated version asap. I will also update the testing NMU[2], which I
> fortunately did not upload yet.

Perfect, thank you for that!

Regards,
Salvatore

Bug#933991: src:libxcomposite: depends on empty transitional package x11proto-composite-dev

[Ferenc Wágner]

Package: src:libxcomposite
Version: 1:0.4.4-2
Severity: normal

Dear Maintainer,

x11proto-composite-dev is a "transitional dummy package" by its
description, and indeed empty, but I can't remove it from my system
because libxcomposite-dev depends on it (and the libxcomposite source
package build-depends on it).  Please consider dropping this dependency.
(BTW, there are similar problems with the other x11proto-*-dev dummy
packages, libx11(-dev) depends on some of them, etc.)
-- 
Thanks,
Feri.

Bug#933990: ITP: bitwise -- Terminal based bit manipulator in ncurses

[Ramon Fried]

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

* Package name: bitwise
  Version : 0.33
  Upstream Author : Ramon Fried 
* URL : https://github.com/mellowcandle/bitwise
* License : GPL3
  Programming Lang: C
  Description : Interactive bitwise operation in ncurses

Bitwise is multi base interactive calculator supporting dynamic base
conversion and bit manipulation. It's a handy tool for low level
hackers, kernel developers and device drivers developers.

Some of the features include:
Interactive ncurses interface
Command line calculator.
Individual bit manipulator.
Bitwise operations such as NOT, OR, AND, XOR, and shifts.

Bug#933989: RM: python-park -- ROM; Python 2 only, no reverse (b-)depends

[Daniele Tricoli]

Package: ftp.debian.org
Severity: normal

Hi,

python-park is a Python 2 only library that was packaged as a dependency
of python-cobe. python-cobe don't use it anymore (or upstream changed
idea, I don't recall correctly). Please remove this package.

Kind regards,
Daniele Tricoli (eriol)

Bug#933950: gamemode 1.4 uploaded to debian unstable

[Yaroslav Halchenko]

THANK YOU Jonathan!

I (and hopefully Mario who knows more) will try to test to the best of my
abilities and whine back if I run into the issues.

meanwhile  could you please also push tags?

$> debcheckout gamemode
declared git repository at https://salsa.debian.org/games-team/gamemode.git
git clone https://salsa.debian.org/games-team/gamemode.git gamemode ...
Cloning into 'gamemode'...
remote: Enumerating objects: 103, done.
remote: Counting objects: 100% (103/103), done.
remote: Compressing objects: 100% (39/39), done.
remote: Total 103 (delta 46), reused 86 (delta 38)
Receiving objects: 100% (103/103), 11.16 KiB | 3.72 MiB/s, done.
Resolving deltas: 100% (46/46), done.
repository only contains the debian directory, using apt-get source
Reading package lists... Done
NOTICE: 'gamemode' packaging is maintained in the 'Git' version control system 
at:
https://salsa.debian.org/games-team/gamemode.git
Please use:
git clone https://salsa.debian.org/games-team/gamemode.git
to retrieve the latest (possibly unreleased) updates to the package.
Need to get 70.5 kB of source archives.
Get:1 http://cdn-fastly.deb.debian.org/debian sid/main gamemode 
1.4+git20190722.4ecac89-1 (dsc) [2,350 B]
Get:2 http://cdn-fastly.deb.debian.org/debian sid/main gamemode 
1.4+git20190722.4ecac89-1 (tar) [64.9 kB]
Get:3 http://cdn-fastly.deb.debian.org/debian sid/main gamemode 
1.4+git20190722.4ecac89-1 (diff) [3,320 B]
Fetched 70.5 kB in 1s (100 kB/s)
dpkg-source: info: extracting gamemode in gamemode-1.4+git20190722.4ecac89
dpkg-source: info: unpacking gamemode_1.4+git20190722.4ecac89.orig.tar.xz
dpkg-source: info: unpacking gamemode_1.4+git20190722.4ecac89-1.debian.tar.xz

$> git -C gamemode tag 

$> 


so there is no tags at all :-/


-- 
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834   Fax: +1 (603) 646-1419
WWW:   http://www.linkedin.com/in/yarik

Bug#933972: policyd-weight: using IPv6 broken in buster

[Werner Detter]

Addition: should be s-p-u'ed

Am 05.08.19 um 21:04 schrieb Werner Detter:
> Hi,
> 
> thanks for your report. Yes, using "use IO::Socket::INET6" addresses
> the issue. libio-socket-inet6-perl is listed in control / Depends. I
> will fix this in the next version.
> 
> Cheers,
> Werner
> 
> 
> 
> Am 05.08.19 um 18:49 schrieb Markus Gschwendt:
>> Package: policyd-weight
>> Version: 0.1.15.2-12
>>
>> After dist-upgrade from stretch to buster:
>>
>> # service policyd-weight restart 
>> [] Restarting policyd-weight configuration (incl. cache): policyd-
>> weightCan't locate object method "new" via package "IO::Socket::INET6"
>> (perhaps you forgot to load "IO::Socket::INET6"?) at /usr/sbin/policyd-
>> weight line 921.
>>  failed!
>>
>> Solution:
>>
>> File
>> /usr/sbin/policyd-weight
>> is not loading the module IO::Socket::INET6.
>> around line 72 following should be inserted:
>> use IO::Socket::INET6;
>>
>> Maybe th
>> Markus
>>
> 

Bug#933988: kubernetes: CVE-2019-11247: API server allows access to custom resources via wrong scope

[Salvatore Bonaccorso]

Source: kubernetes
Version: 1.7.16+dfsg-1
Severity: grave
Tags: security upstream
Forwarded: https://github.com/kubernetes/kubernetes/issues/80983

Hi,

The following vulnerability was published for kubernetes.

CVE-2019-11247[0]:
API server allows access to custom resources via wrong scope

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-2019-11247
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11247
[1] https://github.com/kubernetes/kubernetes/issues/80983

Regards,
Salvatore

Bug#933987: openvpn-systemd-resolved: update-systemd-resolved.conf confuses openvpn@.service

[David Bremner]

Package: openvpn-systemd-resolved
Version: 1.3.0-2
Severity: normal


I'm not sure if this is a but in openvpn or in this package, but the
presence of update-systemd-resolved.conf in /etc/openvpn confuses the
(old) openvpn@.service template, which thinks it represents a network
instance.

This leads to an endless attempt to start the network on boot (by default, 
unless e.g. masked)

sample log

Aug 05 14:55:36 convex systemd[1]: openvpn@update-systemd-resolved.service: 
Service RestartSec=5s expired, schedul
Aug 05 14:55:36 convex systemd[1]: openvpn@update-systemd-resolved.service: 
Scheduled restart job, restart counter
Aug 05 14:55:36 convex systemd[1]: Stopped OpenVPN connection to 
update-systemd-resolved.
Aug 05 14:55:36 convex systemd[1]: Starting OpenVPN connection to 
update-systemd-resolved...
Aug 05 14:55:36 convex ovpn-update-systemd-resolved[1750]: Options error: --up 
script fails with '/etc/openvpn/scr
Aug 05 14:55:36 convex ovpn-update-systemd-resolved[1750]: Options error: 
Please correct this error.
Aug 05 14:55:36 convex ovpn-update-systemd-resolved[1750]: Use --help for more 
information.
Aug 05 14:55:36 convex systemd[1]: openvpn@update-systemd-resolved.service: 
Main process exited, code=exited, st

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

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

Versions of packages openvpn-systemd-resolved depends on:
ii  libnss-resolve  241-7
ii  openvpn 2.4.7-1
ii  systemd 241-7

openvpn-systemd-resolved recommends no packages.

openvpn-systemd-resolved suggests no packages.

-- no debconf information

Bug#933986: nmu: pygalmesh_0.3.6-1

[Joachim Reichel]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu

Hi,

I uploaded a new version of cgal which bumped the SOVERSION of
libCGAL_ImageIO.so and was not aware that there is nowadays a reverse
dependency of this library in Debian.

  nmu pygalmesh_0.3.6-1 . ANY . unstable . -m "Rebuild against 
libCGAL_ImageIO.so.14"

Thanks,
  Joachim


-- System Information:
Debian Release: 10.0
  APT prefers stable-debug
  APT policy: (800, 'stable-debug'), (800, 'stable'), (700, 'testing-debug'), 
(700, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#933622: formiko: ampersand escaping issues: Error on line 1: Entity did not end with a semicolon

[Ondřej Tůma]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Thanks for your bug report,

bug is fixed in upstream git, and will be fixed in debian with new
version.

Ondra


V Thu, 01 Aug 2019 11:28:04 +0800
Paul Wise  napsáno:

> Package: formiko
> Version: 1.3.0-1
> Severity: normal
> Usertags: warnings
> 
> When I load a markdown document containing links that have the
> ampersand (&) character in them, I get messages like this on the
> terminal where I launched Formiko:
> 
> (formiko:11739): Gtk-WARNING **: 10:44:45.901: Failed to set text
> ' link: 
> https://wiki.debian.org/Teams/ReleaseTeam/ReleaseCheckList?action=diff=85=83
> ' from markup due to error parsing markup: Error on line 1:
> Entity did not end with a semicolon; most likely you used an ampersand
> character without intending to start an entity — escape ampersand as
> 
> 
> It seems that Formiko doesn't properly escape the ampersands to HTML
> () when converting markdown to HTML.
> 
> -- System Information:
> Debian Release: bullseye/sid
>   APT prefers testing-debug
>   APT policy: (900, 'testing-debug'), (900, 'testing'), (800,
> 'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700,
> 'experimental-debug'), (700, 'experimental'), (690,
> 'buildd-experimental') Architecture: amd64 (x86_64)
> 
> Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
> Kernel taint flags: TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE,
> TAINT_UNSIGNED_MODULE Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8
> (charmap=UTF-8), LANGUAGE=en_AU.utf8 (charmap=UTF-8) Shell: /bin/sh
> linked to /bin/dash Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
> 
> Versions of packages formiko depends on:
> ii  gir1.2-gtksource-3.0  3.24.9-2
> ii  gir1.2-gtkspell3-3.0  3.0.9-3
> ii  gir1.2-webkit2-4.02.24.3-1
> ii  python3   3.7.3-1
> ii  python3-docutils  0.14+dfsg-4
> ii  python3-gi3.30.4-1
> ii  python3-recommonmark  0.4.0+ds-5
> 
> formiko recommends no packages.
> 
> Versions of packages formiko suggests:
> pn  vim-gtk3  
> 
> -- no debconf information
> 

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEdlj+NNFMWaEf/Gl1Bd+niyV86poFAl1IfEgACgkQBd+niyV8
6prZkA/+LcR5KrDbZIA19+2xIXi351I6yQkyNH5XmERNqrsK/Ci8fl5OwFf3JWhI
6eou7/RzzTUjrYCs9ctKwIDtgZng0CDUTO2dV2B3edmIeyJZbFcY/zAnB+VQ8mG2
HKdL/+q1aQezCXEHD0FXZKqnNCtFV2OQjMKF6Rk9nEdD+PKw4Uy6ybiePNVuGnAe
VqkmyXrpsSsYk5EvmtaRXIR+lMvS1nRB+gYdFmMpDGut9I99apMhKMrXTEwUcWUK
C8dXQQEg7H6g43tnP+EOoPpn+FKqUDGOY6oRJXpR0+p94tAMtBHRFQ6Ig8Wy1Abk
ny5kwOsfBoOWkPqB0qF+gphaodRGJtVDjOYTPzOXSnt9pV9ka7eqbusnVew2A8Kp
daNa0ZPSzvlBVhbBo/e0N22AiA4Qh0eoTMq8+41NMhfTqb8UbvqlmAy9i4m/dHQ7
CODamagBYhY3QpSyp97zB9r/DiIwC+iKTamEP5vnhy8zhWqYoR3DCd13P8iI91A6
beJyN5l1pcyKg2nvSeP6PBVWjxQZdz/P89rfjWsmd6SRFbBqnfqVRahNushUYDUw
PnuRLQMMAgzOuYFmMi9qjcZsTfcxV+xMgeFKKsiILnp+lnMkVLWzSth2wctJ3Lw9
rZUDW5glwoRJGPLfQPK72zQMBrJ5qKnnTWh8R1h57kSW9hYg1UA=
=fsar
-END PGP SIGNATURE-

Bug#933464: saga: Please rebuild against wxWidgets GTK 3 package

[Johan Van de Wauw]

FYI. I've done some testing and didn't see any issues when using the
wxWidgets GTK3 build.

Bug#933972: policyd-weight: using IPv6 broken in buster

[Werner Detter]

Hi,

thanks for your report. Yes, using "use IO::Socket::INET6" addresses
the issue. libio-socket-inet6-perl is listed in control / Depends. I
will fix this in the next version.

Cheers,
Werner



Am 05.08.19 um 18:49 schrieb Markus Gschwendt:
> Package: policyd-weight
> Version: 0.1.15.2-12
> 
> After dist-upgrade from stretch to buster:
> 
> # service policyd-weight restart 
> [] Restarting policyd-weight configuration (incl. cache): policyd-
> weightCan't locate object method "new" via package "IO::Socket::INET6"
> (perhaps you forgot to load "IO::Socket::INET6"?) at /usr/sbin/policyd-
> weight line 921.
>  failed!
> 
> Solution:
> 
> File
> /usr/sbin/policyd-weight
> is not loading the module IO::Socket::INET6.
> around line 72 following should be inserted:
> use IO::Socket::INET6;
> 
> Maybe th
> Markus
> 

Bug#933958: The golang FTBFS on amd64 should be fixed

[Shengjing Zhu]

Hi,

On Tue, Aug 6, 2019 at 2:03 AM Dr. Tobias Quathamer  wrote:
>
> the FTBFS of golang should be fixed. It was due to the GOCACHE changes
> from Go 1.11 to Go 1.12. Anthony Fok has just fixed this in dh-golang.
>

The golang compiler doesn't build depends dh-golang. So any change in
dh-golang won't fix the compiler itself.

-- 
Shengjing Zhu

Bug#933985: cups: Fix retrospectively CVE id for CVE-2018-4300 in debian/changelog

[Salvatore Bonaccorso]

Source: cups
Version: 2.2.10-1
Severity: minor

Hi

There was  confusion and typo on one CVE id for a CVE-2018-4300. See
https://github.com/apple/cups/issues/5561 for details (the CVE id was
later on as well fixed retrospectively upstream in NEWS/changelogs).

To avoid confusions, and if this fits the printing team packaging
practices, could you rectify the CVE identifier mentioned in the
debian/changelog as well? Otherwise feel free to mark this one as
wontfix and close it.

Regards,
Salvatore

Bug#933976: buster-pu: package nx-libs/2:3.5.99.19-3+deb10u1

[Mike Gabriel]

Hi Adam,

On  Mo 05 Aug 2019 20:29:10 CEST, Adam D. Barratt wrote:


Control: tags -1 + moreinfo

On Mon, 2019-08-05 at 19:46 +0200, Mike Gabriel wrote:

I just uploaded nx-libs 2:3.5.99.19-3+deb10u1 to buster containing
various patches from a recently performed memleak hunt by one of the
nx-libs upstream developers.



What's the plan for getting the fixed applied in unstable? That's (as
always) a pre-requisite to fixing issues in stable, but buster and sid
appear to have the same version of nx-libs currently.

Regards,

Adam


I am sorry, you are right, I haven't kept the correct upload order.  
For unstable, I am currently preparing a 2:3.5.99.21-1 upload (all  
patches applied in that release).


Mike
--

DAS-NETZWERKTEAM
c\o Technik- und Ökologiezentrum Eckernförde
Mike Gabriel, Marienthaler str. 17, 24340 Eckernförde
mobile: +49 (1520) 1976 148
landline: +49 (4351) 850 8940

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de



pgpO8XnPC2deZ.pgp
Description: Digitale PGP-Signatur

Bug#933886: AppArmor configuration doesn't cover userscripts

[Martin Wolf]

Hello Carsten,

ty, I am glad I can help a little ...

Kopano must have changed the directories in Summer last year. I ran into
it, when I updated my productive system (that will get replaced with
Debian 10 + 8.7.0)  to a nightly of 8.6.81.xxx end of August 2018.

Regards

Martin




pEpkey.asc
Description: application/pgp-keys

Bug#933535: buster-pu: package glib2.0/2.58.3-2+deb10u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Wed, 2019-07-31 at 11:13 +0100, Simon McVittie wrote:
> GLib in buster is vulnerable to CVE-2019-13012 (configuration files
> and directories created with more open permissions than intended),
> which the security team have indicated is too minor for a DSA.
> 
> 
> GLib has a udeb, so this technically needs a d-i ack, although I
> can't imagine why d-i would either use GKeyfileSettingsBackend or
> care about the resulting permissions.

It does seem rather unlikely, but let's do the CC-for-ack dance in any
case.

Regards,

Adam

Bug#933983: RM: storm/0.19-2 -- RoQA; orphaned; no Py2 and no revdeps

[Adam D. Barratt]

On Mon, 2019-08-05 at 23:31 +0500, Andrey Rahmatullin wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: rm
> 
> Orphaned, doesn't support Python 2, doesn't have revdeps (checked
> with `dak rm
> -Rn storm`).
> 
> No Py3 support upstream either: https://bugs.launchpad.net/storm/+bug
> /1530734

>From which suite?

Regards,

Adam

Bug#933971: linux-image-4.19.0-5-marvell: Kernel fails to parse mtdparts arg in cmdline. Impacts usage of fw_setenv on plug devices to config uboot.

[Ben Hutchings]

On Mon, 2019-08-05 at 20:30 +0200, Evrard, Benjamin wrote:
> It is indeed the same bug and the proposed workaround works fine.
> 
> Still, I think that the choice of compiling the corresponding driver
> as a module instead of embedding it in the kernel is a decision that
> will impact many users when they upgrade their plug device from Debian
> Stretch to Buster.
> 
> Most of them are bound to meet the same issue.
> 
> Any chance this choice would be reconsidered?

I didn't mean to imply that the bug won't be fixed.

Ben.

-- 
Ben Hutchings
Beware of programmers who carry screwdrivers. - Leonard Brandwein




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

Bug#933984: RM: pyramid-beaker/0.6.1+ds1-1 -- RoM; no Py3 and no revdeps

[Andrey Rahmatullin]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: rm

No Python 3 support. No revdeps (checked with dak rm -Rn pyramid-beaker).

Newer upstream versions declare Python 3.2 compatibility. Last release in 2013.

Bug#933983: RM: storm/0.19-2 -- RoQA; orphaned; no Py2 and no revdeps

[Andrey Rahmatullin]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: rm

Orphaned, doesn't support Python 2, doesn't have revdeps (checked with `dak rm
-Rn storm`).

No Py3 support upstream either: https://bugs.launchpad.net/storm/+bug/1530734

Bug#933886: AppArmor configuration doesn't cover userscripts

[Carsten Schoenert]

Control: tags -1 pending

Hello Martin,

nice catch!

On Sun, Aug 04, 2019 at 11:02:51PM +0200, Martin Wolf wrote:
> Package: kopano-server
> Version: 8.7.0-3
> 
> The default AppArmor configuration file
> /etc/apparmor.d/usr.sbin.kopano-server doesn't cover the default
> userscripts in /usr/lib/kopano/userscripts/*, which are required to e.g.
> create or delete a new user (or a company/tenancy), thus basically
> everything. The AppArmor configuration however covers individual
> userscripts in /etc/kopano/userscripts/* somehow, while
> /etc/kopano/userscripts/* doesn't exist by default and
> /usr/lib/kopano/userscripts/* is referenced in /etc/kopano/server.cfg as
> default.

So far I remember the folder in /etc was the old default before 8.6.x,
but we didn't updated the AppArmor profile for the server accordingly
after that change.

> Adding "  /usr/lib/kopano/userscripts/* Cxr -> kopano_userscripts," to
> /etc/apparmor.d/usr.sbin.kopano-server seems to help.

I've modified modify the current rule in usr.sbin.kopano-server to adopt the
current default.

Regards
Carsten

Bug#933920: src:python-markdown: Unsafe use of yaml.load()

[Dmitry Shachnev]

Hi Scott!

On Mon, Aug 05, 2019 at 01:32:46AM -0400, Scott Kitterman wrote:
> Package: src:python-markdown
> Version: 3.0.1-3
> Severity: grave
> Tags: security
> Justification: user security hole
>
> The new version of pyyaml no longer allows use of yaml.load() without a
> loader being specifed.  This raises a deprecation warning which has
> caused and autopkgtest failure on this package.  These are generally
> trivial to fix, see the upstream guidance [1].

I will now fix the use of yaml.load() for compatibility with pyyaml 5.1
(by uploading the new upstream release to unstable), but the new version
will still use unsafe_load(). Please see this upstream change:

https://github.com/Python-Markdown/markdown/pull/806

As the upstream comment explains, “We use unsafe_load because users may
need to pass in actual Python objects. As this is only available from
the CLI, the user has much worse problems if an attacker can use this
as an attack vector”.

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Bug#933971: linux-image-4.19.0-5-marvell: Kernel fails to parse mtdparts arg in cmdline. Impacts usage of fw_setenv on plug devices to config uboot.

[Evrard, Benjamin]

It is indeed the same bug and the proposed workaround works fine.

Still, I think that the choice of compiling the corresponding driver
as a module instead of embedding it in the kernel is a decision that
will impact many users when they upgrade their plug device from Debian
Stretch to Buster.

Most of them are bound to meet the same issue.

Any chance this choice would be reconsidered?

Le lun. 5 août 2019 à 18:42, Ben Hutchings  a écrit :
>
> This appears to be the same as bug #931852, where you will find a
> workaround: .
>
> Ben.
>
> --
> Ben Hutchings
> Beware of programmers who carry screwdrivers. - Leonard Brandwein
>

Bug#933981: cdrom: USB, KVM create connect/disconnect loop in level1 (repair) install

[Tom Sullivan]

Package: cdrom
Severity: grave
Tags: d-i
Justification: renders package unusable

Dear Maintainer,

   * What led up to the situation?

I had another machine that gave kernel panic while upgrading from Stretch to
Buster. Use of Graphical install was also a problem during re-install due to
destroyed system. (I reported this issue in another report.) Thus, I chose to
upgrade an identical machine from level 1 (Debain Repair in GRUB2 boot menu).

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

The scrolling log in the command line display showed repeated
connect/disconnect loops for USB devices (of many kinds). This applied also to
USB mice and keyboards connected via KVM.

For what it was worth, I used a local cache of the DVDs on the machine's hard
drive.

Unplugged all USB, plugged in single USB keyboard only, and directly, not via
KVM.

   * What was the outcome of this action?

Upgraded fine with just the keyboard directly plugged into USB.

   * What outcome did you expect instead?

Correct handling of USB, without issues.




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

Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), 
LANGUAGE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#933982: bash: normalize video with ffmpeg corrupts variable bash in the while/done loop

[Antonio]

Package: bash
Version: 5.0-4
Severity: normal

Dear Maintainer,
today, while I was writing a script for normalize video, I noticed a
strange interaction between "while ... done" (bash script) and program
"ffmpeg".


Here is a simple example to reproduce the problem.


# get a simple video mp4 for testing
wget -c http://techslides.com/demos/sample-videos/small.mp4


# copy url in a variable
url="http://techslides.com/demos/sample-videos/small.mp4;



# create a variable by repeating this line (separating the url with a space)
manyurl="$url $url $url $url $url $url $url $url $url $url $url $url
$url $url $url $url $url $url $url $url"


# convert to a variable containing the same url as lines for test and display it
manyurl_lines="$(for x in $manyurl; do echo $x; done)"
echo -e "$manyurl_lines"


# output (as expected)http://techslides.com/demos/sample-videos/small.mp4
...http://techslides.com/demos/sample-videos/small.mp4


# if I now normalize the same file several times, this process
interferes with the variable "f" in the loop, eating some initial
characters randomly
while read -r f; do echo $f; ffmpeg -y -i "small.mp4" -af
loudnorm=I=-14:TP=-3:LRA=11:print_format=json -f null -
"small_normalized.mp4" &>/dev/null; done <<< "$manyurl_lines"


# output 
(why?):http://techslides.com/demos/sample-videos/small.mp4techslides.com/demos/sample-videos/small.mp4techslides.com/demos/sample-videos/small.mp4techslides.com/demos/sample-videos/small.mp4techslides.com/demos/sample-videos/small.mp4techslides.com/demos/sample-videos/small.mp4techslides.com/demos/sample-videos/small.mp4techslides.com/demos/sample-videos/small.mp4techslides.com/demos/sample-videos/small.mp4techslides.com/demos/sample-videos/small.mp4techslides.com/demos/sample-videos/small.mp4
/techslides.com/demos/sample-videos/small.mp4techslides.com/demos/sample-videos/small.mp4techslides.com/demos/sample-videos/small.mp4techslides.com/demos/sample-videos/small.mp4
/techslides.com/demos/sample-videos/small.mp4techslides.com/demos/sample-videos/small.mp4techslides.com/demos/sample-videos/small.mp4techslides.com/demos/sample-videos/small.mp4techslides.com/demos/sample-videos/small.mp4


# but if I use the "for ... done" construct this does not happen:
for f in $manyurl_lines; do echo $f; ffmpeg -y -i "small.mp4" -af
loudnorm=I=-14:TP=-3:LRA=11:print_format=json -f null -
"small_normalized.mp4" &>/dev/null; done


# output (as expected)http://techslides.com/demos/sample-videos/small.mp4
...http://techslides.com/demos/sample-videos/small.mp4


# or if comment ffmpeg in the "while ... done":
while read -r f; do echo $f; :ffmpeg -y -i "small.mp4" -af
loudnorm=I=-14:TP=-3:LRA=11:print_format=json -f null -
"small_normalized.mp4" &>/dev/null; done <<< "$manyurl_lines"


# output (as expected)http://techslides.com/demos/sample-videos/small.mp4
...http://techslides.com/demos/sample-videos/small.mp4
there is an explanation for this?

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

Kernel: Linux 5.2.6-custom (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=it_IT, LC_CTYPE=it_IT (charmap=ISO-8859-1) (ignored:
LC_ALL set to it_IT), LANGUAGE=it (charmap=ISO-8859-1) (ignored:
LC_ALL set to it_IT)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages bash depends on:
ii  base-files   11
ii  debianutils  4.8.6.3
ii  libc62.28-10
ii  libtinfo66.1+20190713-2

Versions of packages bash recommends:
ii  bash-completion  1:2.8-7

Versions of packages bash suggests:
pn  bash-doc  

-- no debconf information

Bug#933976: buster-pu: package nx-libs/2:3.5.99.19-3+deb10u1

[Adam D. Barratt]

Control: tags -1 + moreinfo

On Mon, 2019-08-05 at 19:46 +0200, Mike Gabriel wrote:
> I just uploaded nx-libs 2:3.5.99.19-3+deb10u1 to buster containing
> various patches from a recently performed memleak hunt by one of the
> nx-libs upstream developers.
> 

What's the plan for getting the fixed applied in unstable? That's (as
always) a pre-requisite to fixing issues in stable, but buster and sid
appear to have the same version of nx-libs currently.

Regards,

Adam

Bug#933980: journalctl --grep fails to work

[Rob Leslie]

Package: systemd
Version: 241-5
Severity: normal
File: /bin/journalctl

Dear Maintainer,

The way journalctl is currently built prevents searching messages by
regular expression:

  % journalctl -g foo
  Compiled without pattern matching support

Could this be made to work?

Thanks.


-- Package-specific info:

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

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

Versions of packages systemd depends on:
ii  adduser  3.118
ii  libacl1  2.2.53-4
ii  libapparmor1 2.13.2-10
ii  libaudit11:2.8.4-3
ii  libblkid12.33.1-0.1
ii  libc62.28-10
ii  libcap2  1:2.25-2
ii  libcryptsetup12  2:2.1.0-5
ii  libgcrypt20  1.8.4-5
ii  libgnutls30  3.6.7-4
ii  libgpg-error01.35-1
ii  libidn11 1.33-2.2
ii  libip4tc01.8.2-4
ii  libkmod2 26-1
ii  liblz4-1 1.8.3-1
ii  liblzma5 5.2.4-1
ii  libmount12.33.1-0.1
ii  libpam0g 1.3.1-5
ii  libseccomp2  2.3.3-4
ii  libselinux1  2.8-1+b1
ii  libsystemd0  241-5
ii  mount2.33.1-0.1
ii  util-linux   2.33.1-0.1

Versions of packages systemd recommends:
ii  dbus1.12.16-1
ii  libpam-systemd  241-5

Versions of packages systemd suggests:
pn  policykit-1
pn  systemd-container  

Versions of packages systemd is related to:
pn  dracut   
ii  initramfs-tools  0.133
ii  udev 241-5

-- no debconf information

Bug#933979: gnutls28: FTBFS on i386: Build killed with signal TERM after 150 minutes of inactivity after dtls/dtls test

[Thorsten Glaser]

Source: gnutls28
Version: 3.6.9-3
Severity: serious
Justification: FTBFS on release arch

From: 
https://buildd.debian.org/status/fetch.php?pkg=gnutls28=i386=3.6.9-3=1564822578=0


[…]
SKIP: p11-kit-trust.sh  
 
PASS: system-override-kx.sh 
 
PASS: certtool-pkcs11.sh
 
PASS: danetool.sh   
 
PASS: gnutls-cli-invalid-crl.sh 
 
PASS: dtls/dtls 
 
E: Build killed with signal TERM after 150 minutes of inactivity
 

 
Build finished at 2019-08-03T08:56:12Z