Re: duplicate popularity-contest ID

On Aug 05, Bill Allombert wrote: > Each Debian popularity-contest submitter is supposed to have > a different random 128bit popcon ID. > However, the popularity-constest server > receives a lot of submissions with identical popcon ID, which cause them > to be treated a

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

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 Descri

Re: do packages depend on lexical order or {daily,weekly,monthly} cron jobs?

On 2019-08-05 17:34, Ian Jackson wrote: With current code the options are: A. Things run in series but with concatenated output and no individual status. B. Things run in parallel, giving load spikes and possible concurrency bugs; vs. I can see few people who would choose (B). People wh

Bug#933973: marked as done (general: System totally freeze all the time (Debian 10))

Your message dated Mon, 5 Aug 2019 21:39:45 +0200 (CEST) with message-id and subject line has caused the Debian Bug report #933973, regarding general: System totally freeze all the time (Debian 10) to be marked as done. This means that you claim that the problem has been dealt with. If this is n

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

Package: wnpp Severity: wishlist Owner: Ramon Fried X-Debbugs-CC: debian-devel@lists.debian.org * Package name: bitwise Version : 0.33 Upstream Author : Ramon Fried * URL : https://github.com/mellowcandle/bitwise * License : GPL3 Programming Lang: C Descri

Bug#933973: general: System totally freeze all the time (Debian 10)

Package: general Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? I don't know! This happens every day by different reasons. * What exactly did you do (or not do) that was effective (or

Bug#933969: ITP: r-cran-corrplot -- Visualization of a Correlation Matrix

Package: wnpp Severity: wishlist Owner: Steffen Moeller * Package name: r-cran-corrplot * URL : https://cran.r-project.org/package=corrplot * License : MIT Programming Lang: R Description : Visualization of a Correlation Matrix Team maintained on https://salsa.deb

Re: duplicate popularity-contest ID

Bill Allombert writes: > Each Debian popularity-contest submitter is supposed to have a different > random 128bit popcon ID. However, the popularity-constest server > receives a lot of submissions with identical > popcon ID, which cause them to be treated as a single

Re: do packages depend on lexical order or {daily,weekly,monthly} cron jobs?

Marc Haber writes ("Re: do packages depend on lexical order or {daily,weekly,monthly} cron jobs?"): > On Mon, 29 Jul 2019 18:42:34 +0100, Simon McVittie > wrote: > >On Wed, 24 Jul 2019 at 20:14:22 +0200, Marc Haber wrote: > >> Scripts with such dependencies will probably fail miserably on systems

Bug#933965: ITP: ecbuild -- ECMWF build system based on CMake

Package: wnpp Severity: wishlist Owner: Alastair McKinstry * Package name: ecbuild Version : 3.0.3 Upstream Author : ECMWF * URL : https://github.com/ecmwf/ecbuild * License : Apache Programming Lang: CMake Description : ECMWF build system based on CMak

Re: duplicate popularity-contest ID

On 2019-08-05 15:29, Bill Allombert wrote: > However, the popularity-constest server > receives a lot of submissions with identical popcon ID, which cause them > to be treated as a single submission. I would suspect cloned VMs to have identical popcon IDs. In this case

Re: duplicate popularity-contest ID

On Mon, Aug 05, 2019 at 02:29:33PM +0200, Bill Allombert wrote: > Dear Debian developers, > > Each Debian popularity-contest submitter is supposed to have > a different random 128bit popcon ID. > However, the popularity-constest server > receives a lot of submissions wi

Re: duplicate popularity-contest ID

Hey Yao and Bill On 2019/08/05 14:31, "Yao Wei (魏銘廷)" wrote: >> I am not quite sure what it is the reason for this problem. >> Maybe people use prebuild system images with a pregenerated >> /etc/popularity-contest.conf file (instead of being generated >> by popcon postinst). > > Could this be cau

Re: duplicate popularity-contest ID

> On Aug 5, 2019, at 20:29, Bill Allombert wrote: > > I am not quite sure what it is the reason for this problem. > Maybe people use prebuild system images with a pregenerated > /etc/popularity-contest.conf file (instead of being generated > by popcon postinst). Could this be caused by Debian-

duplicate popularity-contest ID

Dear Debian developers, Each Debian popularity-contest submitter is supposed to have a different random 128bit popcon ID. However, the popularity-constest server receives a lot of submissions with identical popcon ID, which cause them to be treated as a single submissio

Re: unsigned repositories

On Mon, 05 Aug 2019 at 10:11:07 +0200, David Kalnischkies wrote: > On Mon, Jul 29, 2019 at 08:01:47AM +0100, Simon McVittie wrote: > > sbuild also uses aptitude instead of apt (for its more-backports-friendly > > resolver) in some configurations, and that doesn't have --with-source. > > JFTR: apti

Re: unsigned repositories

On Mon, 05 Aug 2019 at 10:09:09 +0200, David Kalnischkies wrote: > So far all usecases mentioned here seem to be local repositories > though. Nobody seems to be pulling unsigned repositories over the > network [for good reasons]. On CI systems at work, I've often found it to be useful to use [trus

Re: unsigned repositories

Hi, Quoting David Kalnischkies (2019-08-05 10:09:09) > So far all usecases mentioned here seem to be local repositories though. > Nobody seems to be pulling unsigned repositories over the network [for good > reasons]. So perhaps we can agree on dropping support for unsigned > repositories for ever

Re: What compiler flags are allowed in unstable/testing

Hi Joël, > What compiler flags are allowed for optimization with gcc in debian > unstable/testing? I'd go with "none". The default CPU architecture in the compiler is the architecture baseline. > My project has got support for builtin vector functions. And we don't > enable any compiler flags to

Re: unsigned repositories

On Mon, Jul 29, 2019 at 08:01:47AM +0100, Simon McVittie wrote: > sbuild also uses aptitude instead of apt (for its more-backports-friendly > resolver) in some configurations, and that doesn't have --with-source. JFTR: aptitude (and all other libapt-based frontends) can make use of that feature vi

Re: unsigned repositories

On Mon, Jul 29, 2019 at 10:53:45AM +0200, Johannes Schauer wrote: > squeeze ended, we finally were able to remove a few hundred lines of code from Julian is hoping that removing support for unsigned repositories would do the same for us with the added benefit that for apt these lines are security