Re: autoremovals a month early?

2019-07-22 Thread Russ Allbery
Steve Robbins  writes:

> What gives?

> Saturday: digikam 4:5.9.0-1 is marked for autoremoval from testing on 
> 2019-08-26

> Sunday: digikam REMOVED from testing

Looks like two different (albeit related) reasons.  The autoremoval
message was:

> It (build-)depends on packages with these RC bugs:
> 931970: gphoto2: autopkgtest failure block readline migration

which is automatic due to depending on a package with an RC bug.  The
actual removal was a manual hint by a human:

>   Previous version: 4:5.9.0-1
>   Current version:  (not in testing)
>   Hint: 
> # 20190721
> # temporary removal to unblock readline transition

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



autoremovals a month early?

2019-07-22 Thread Steve Robbins
What gives?

Saturday: digikam 4:5.9.0-1 is marked for autoremoval from testing on 
2019-08-26

Sunday: digikam REMOVED from testing

-S
--- Begin Message ---
FYI: The status of the digikam source package
in Debian's testing distribution has changed.

  Previous version: 4:5.9.0-1
  Current version:  (not in testing)
  Hint: 
# 20190721
# temporary removal to unblock readline transition

The script that generates this mail tries to extract removal
reasons from comments in the britney hint files. Those comments
were not originally meant to be machine readable, so if the
reason for removing your package seems to be nonsense, it is
probably the reporting script that got confused. Please check the
actual hints file before you complain about meaningless removals.

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.
--- End Message ---
--- Begin Message ---
digikam 4:5.9.0-1 is marked for autoremoval from testing on 2019-08-26

It (build-)depends on packages with these RC bugs:
931970: gphoto2: autopkgtest failure block readline migration


--- End Message ---


Processed: tagging 932769

2019-07-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 932769 - l10n
Bug #932769 [general] general: DHCP request bug when storage lost
Removed tag(s) l10n.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
932769: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932769
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Re: file(1) now with seccomp support enabled

2019-07-22 Thread Chris Lamb
[Adding rb-gene...@lists.reproducible-builds.org to CC]

Hi Christoph,

> Overall, I'm just asking to keep an eye on possible breakage, also
> check the kernel log.

I noticed that there were a number of recent regressions in previously
reproducible Java packages being tested by the Reproducible Builds
project's CI platform which I could identify as being caused by our
strip-nondeterminism tool.

However, as there was a very recent change to some strip-nondeterminism
code that uses "monkey patching" I was predisposed to believe that was
the cause, but it eventually turned out to be the call to file(1)
missing a --no-sandbox parameter (where supported / appropriate).

It did not even occur to check my kernel log as you suggest — it was
only when quickly hacking in a:

override_dh_strip_non_determinism:
strace -eexecve -f dh_strip_nondeterminism

… to my test package that I figured the file(1) process was being
killed (without returning any output) with SIGCHLD that things were
perhaps lower-level in nature. This has been resolved in strip-
nondeterminism 1.3.0, uploaded this afternoon.

This mail is not a request for anything, but rather a general heads-up
for you and a way of "keyword stuffing" various terms the above
paragraphs into search indexes for the benefit of others looking for
perhaps-obscure issue like this in the future. It is also an implicit
thanks for pushing security hardening features. :)


Best wishes,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org 🍥 chris-lamb.co.uk
   `-



Bug#932769: general: DHCP request bug when storage lost

2019-07-22 Thread Mark Hutchison
Package: general
Severity: important
Tags: l10n

Dear Maintainer,

While doing unrelated storage testing for our VMware integrated product, we 
purposefully recreated
a storage outage by removing the iSCSI initiators from the backing array 
hosting the vmdk disk 
images for the virtual machine.

Upon removal of uplinks to storage, the VM goes into a R/O file system state 
after 5-10 minutes.
When storage initiators are brought back up and the LUNs are rescanned, the VM 
begins to 
rapidly request DHCP leases from an ISC DHCP server.  This DoS's the server in 
a way due
to the number of DHCPDECLINE errors, and the interface attempts to take and 
discard IP's in a
rapid fashion. 

This only seems to appear on this distribution, and I can't replicate the 
behavior on Debian 9
or in a desktop environment.



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



Bug#932753: tag2upload should record git tag signer info in .dsc

2019-07-22 Thread Ian Jackson
Package: dgit-infrastructure
Version: 9.4

Raphael Hertzog writes ("Re: git & Debian packaging sprint report"):
> On Sun, 21 Jul 2019, Ian Jackson wrote:
> > IME as a sponsor I get (AFAICT) no mails as a result of my sponsorship
> > signatures so I think there are few automatic processes.
> 
> That's actualy not true, dak is sending mails to the person who signs the
> upload when it has to send mails like NEW notifications, etc.
> 
> > Hrm, I think tracker may become confused.  It seems to be looking at the
> > .dsc signatur.  So maybe the .dsc field is indeed needed.
> 
> Yes, definitely. 

Thanks to all for the info.  I thought I would capture this here in
a bug, which I can mention in my commit messages, giving a link back
to this -devel thread.

The signing robot's key email address will be a mailing list, so any
stray emails will go there.  That's clearly far from perfect but I
don't think it's a blocker for deployment.  (Which is good because
fixing it will involve patching dak and the other things which use
that signing identity.)

Ian.

-- 
Ian JacksonThese opinions are my own.

If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.



Bug#932744: ITP: faultstat -- page fault monitoring tool

2019-07-22 Thread Colin Ian King
Package: wnpp
Severity: wishlist
Owner: Colin Ian King 

* Package name: faultstat
  Version : 0.01.01
  Upstream Author : Colin Ian King 
* URL : https://github.com/ColinIanKing/faultstat
* License : GPL-2
  Programming Lang: C
  Description : page fault monitoring tool

Faultstat reports the page fault activity of processes
running on a system. The tool supports a 'top' like mode
to dynamically display the top page faulting processes.

It is a very lightweight tool (in terms of CPU and memory
utilization) that is useful to find the top major/minor page
faulting processes when performance monitoring a busy system.

As the author of this tool, I plan to maintain this by ensuring
it has zero static analysis warnings and builds cleanly with all
new tool chain updates on a regular basis, much like other tools
I maintain in Debian.



Re: git & Debian packaging sprint report

2019-07-22 Thread Raphael Hertzog
On Sun, 21 Jul 2019, Ian Jackson wrote:
> IME as a sponsor I get (AFAICT) no mails as a result of my sponsorship
> signatures so I think there are few automatic processes.

That's actualy not true, dak is sending mails to the person who signs the
upload when it has to send mails like NEW notifications, etc.

> Hrm, I think tracker may become confused.  It seems to be looking at the
> .dsc signatur.  So maybe the .dsc field is indeed needed.

Yes, definitely. 

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

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



Ważne pytanie

2019-07-22 Thread Agencja Kreatywna

Dzień dobry,


zajmujemy się budową *Stron i Sklepów internetowych* dla firm.


 
Jeśli chcieliby Państwo otrzymać bezpłatną propozycję w tym temacie prosimy o 
odpowiedź *Tak *na ten e-mail.


--

Pozdrawiamy!

Twórcy Stron i Sklepów WWW
(57)



Bug#932726: ITP: python-pyspike -- Python library for the numerical analysis of spike train similarity

2019-07-22 Thread Gard Spreemann
Package: wnpp
Severity: wishlist
Owner: Gard Spreemann 

* Package name: python-pyspike
  Version : 0.6.0
  Upstream Author : Mario Mulansky 
* URL : https://mariomulansky.github.io/PySpike/
* License : BSD-2-clause
  Programming Lang: Python, C
  Description : Python library for the numerical analysis of spike train 
similarity

 PySpike is a Python library for the numerical analysis of spike train
 similarity. Its core functionality is the implementation of the
 ISI-distance and SPIKE-distance as well as SPIKE-Synchronization. It
 provides functions to compute multivariate profiles, distance
 matrices, as well as averaging and general spike train processing.

 Mario Mulansky, Thomas Kreuz, PySpike - A Python library for
 analyzing spike train synchrony, SoftwareX, (2016), ISSN 2352-7110,
 http://dx.doi.org/10.1016/j.softx.2016.07.006.

 The library seems simple and mature, and I will be capable of
 maintaining it on my own.

 I will need a sponsor, and will enquire with the DDs that have
 sponsored packages for me in the past.



Re: Debian and our frenemies of containers and userland repos

2019-07-22 Thread Enrico Weigelt, metux IT consult

On 11.07.19 17:25, Yao Wei wrote:

Hi,


It can be a "solid base" of container images and barebone systems, but
the days are numbered as operating systems as free and focused on its
mission (like Google COOS, Yocto, Alpine etc.) is evolving steady.

Could it be a disaster for us?  And more importantly, do users care?


I don't think so.

COOS:   just yet another special purpose distro, in that case for
docker hosts. neither the first, nor the last one to come.
Yocto:  just yet another compile-yourself distro, focused on embeedded,
that happens to be hyped by certain corporations.
(for small/embedded devices, I'd really recommend ptxdist).
Alpine: yet another distro, optimized for running in small containers

BTW: the idea of building small payload/application-specific 
containers/chroot's is anything but new. I've done it somewhere in

the 90th. But nowadays, these so-called "small" containers tend to be
bigger than whole machines of the 90th.

Containerization is a valid approach for some kind of workloads
(eg. specific inhouse applications) that can be easily isolated from
the rest. But it comes with the price of huge redundancies (depending
on how huge some application stacks are). And unless everybody wants
to go back of maintaining everything on his own, we still need distros.

If different applications need to deeply interact (eg. various plugin
stuff, applications calling each other, etc), containerization doesn't
help much. (eg: how can you have a pure texlive in one container and
extra things like fonts, document classes, etc, in separate ones ? :o)

The whole point about containerization isn't about packaging and
deployment of individual applications - instead it's about automatizing
the rollout of fully-configured installations.

One thing seems to be right: folks who always have been hostile towards
the whole concept of distros now have a better excuse.


--mtx

--
Enrico Weigelt, metux IT consult
Free software and Linux embedded engineering
i...@metux.net -- +49-151-27565287



Paid Guest Posting

2019-07-22 Thread Jason Dunlap
Hi,

We are a Guest Posting services provider and found your blog during our 
outreach campaign. We can do a long-term relationship if you can allow us to 
post a unique, good quality and non-promotional articles on your website. 

We have a team of US and UK native writers to research and write quality 
articles that fit your blog niche. 

Please let me know the price per guest post on your website; we can pay you via 
PayPal for publishing unique articles on your website with one anchor website. 

Will be waiting to have your very positive response! 

Best Regards,

Jason Dunlap.