On Fri, Aug 04, 2017 at 06:20:31PM -0700, Sean Whitton wrote:
> Hello,
>
> On Fri, Aug 04 2017, Adrian Bunk wrote:
>
> > Autogenerating Uploaders like GNOME does [1] would be an alternative
> > approach.
> >
> > [1]
> > https://sources.debian.net/src/gnome-pkg-tools/0.19.9/1/rules/uploaders.mk/
>
On Sat, 05 Aug 2017 at 06:50:00 +, Niels Thykier wrote:
> Can we integrate these LSM policies into our testing frameworks (e.g.
> autopkgtests), so we can start having automated tests of even basic
> functionality. Or will that happen "out of the box" if we enable it by
> default (and, possibl
Hello,
On Sat, Aug 05 2017, Adrian Bunk wrote:
> I assume you are thinking of parsing the [ name ] syntax used by many
> teams.
Yes.
> Note that a prerequisite for such debian/changelog parsing would be
> that policy sets strict syntax and semantics requirements.
No, we do not need to block su
On Friday, August 4, 2017 12:35:04 PM CDT Paul Wise wrote:
> Windows viruses in Debian email packages
>
>
> Sometimes[6] upstreams of email related packages include live Windows
> viruses/malware in their test corpus, either by accident or on purpose,
>
On Sat, 05 Aug 2017 at 09:03:12 -0500, Steve Robbins wrote:
> The news bit refers to "test corpus", so removal would presumably not change
> the output. But I have to wonder: are there not cases where the malware is
> present for *training* a detection system? If so, I would imagine removal
>
On Sat, Aug 5, 2017 at 10:03 AM, Steve Robbins wrote:
> The news item doesn't specify what to do after scanning, but the referenced
> bug requests removal of the offending material.
Personally I would recommend removal, especially since most (but not
all) malware is not DFSG-free. If the malware
On Sat, Aug 05, 2017 at 07:00:16AM -0700, Sean Whitton wrote:
> Hello,
>
> On Sat, Aug 05 2017, Adrian Bunk wrote:
>
> > I assume you are thinking of parsing the [ name ] syntax used by many
> > teams.
>
> Yes.
>
> > Note that a prerequisite for such debian/changelog parsing would be
> > that p
On Sat, Aug 05, 2017 at 04:35:35PM +0200, Bill Allombert wrote:
> > > Note that a prerequisite for such debian/changelog parsing would be
> > > that policy sets strict syntax and semantics requirements.
> >
> > No, we do not need to block such a feature that would work for 90% of
> > packages unti
Hello,
[removing bug against -policy from CC]
On Sat, Aug 05 2017, Bill Allombert wrote:
> How do you get that it would work 90% of package ? Using [] for
> non-team members is very common.
My intent was to discover who is working on a package. It would be okay
for non-team members to be incl
Package: wnpp
Severity: wishlist
Owner: Mike Gabriel
* Package name: python-wither
Version : 1.1
Upstream Author : Da Blitz
* URL : https://pypi.python.org/pypi/wither/
* License : BSD-3-clause
Programming Lang: Python
Description : XML/HTML Generation
On Sat, Aug 05, 2017 at 10:39:02AM +0300, Adrian Bunk wrote:
> > I don't understand this suggestion. If it can be automatically
> > generated, just generate it when you need it -- why store it in the
> > source package?
>
> What cannot be automatically generated is the other side of the
> inters
On Sat, Aug 05, 2017 at 11:30:30AM +0100, Simon McVittie wrote:
> On Sat, 05 Aug 2017 at 06:50:00 +, Niels Thykier wrote:
> > Can we integrate these LSM policies into our testing frameworks (e.g.
> > autopkgtests), so we can start having automated tests of even basic
> > functionality. Or will
intrigeri wrote...
> tl;dr: I hereby propose we enable AppArmor by default in testing/sid,
> and decide one year later if we want to keep it this way in the
> Buster release.
I really appreciate your approach of trying this out while being
prepared this might turn out to be a bad idea. Or: Promot
On Fri, Aug 04, 2017 at 07:31:36PM -0400, intrigeri wrote:
> tl;dr: I hereby propose we enable AppArmor by default in testing/sid,
> and decide one year later if we want to keep it this way in the
> Buster release.
loving it, please go ahead! ;-)
--
cheers,
Holger
signature.asc
Descri
Hi ladies and the ugly kind!
i386:[~]$ chromium
.[ xmessage ]
The hardware on this system lacks support for the sse2 instruction set.
The upstream chromium project no longer supports this configuration.
For more information, please read and posibly provide input to their
bug tracking system at
On Sat, Aug 05, 2017 at 03:19:29PM +, Holger Levsen wrote:
> On Sat, Aug 05, 2017 at 04:35:35PM +0200, Bill Allombert wrote:
> > > > Note that a prerequisite for such debian/changelog parsing would be
> > > > that policy sets strict syntax and semantics requirements.
> > >
> > > No, we do not
On Sat, Aug 05, 2017 at 03:28:57PM +, Holger Levsen wrote:
> On Sat, Aug 05, 2017 at 10:39:02AM +0300, Adrian Bunk wrote:
> > > I don't understand this suggestion. If it can be automatically
> > > generated, just generate it when you need it -- why store it in the
> > > source package?
> >
>
On Sat, Aug 05, 2017 at 09:05:46PM +0300, Adrian Bunk wrote:
> > I think using the uploaders: field to guess who's a team member is just a
> > work-around / an estimate, as we have nothing better.
> It is the official place to list co-maintainers.
you keep repeating this but its still broken by de
One thing that is worth discussing here:
For how many teams would it bring real benefits if they no longer
have to maintain team membership information in every source packages?
My guesstimate is that these might perhaps be 5 teams.
Why is my guestimate so low?
It only brings real benefits for
On Sat, 05 Aug 2017 21:39:40 +0300, Adrian Bunk wrote:
> Regarding the first point, most large teams do have have the concept of
> package ownership inside the team.
Maybe, maybe not.
So far I've seen mostly voices from people working in teams in this
thread who are in favour of dropping the re
gregor herrmann writes:
> On Sat, 05 Aug 2017 21:39:40 +0300, Adrian Bunk wrote:
>
>> Regarding the first point, most large teams do have have the concept of
>> package ownership inside the team.
>
> Maybe, maybe not.
> So far I've seen mostly voices from people working in teams in this
> thread
On 08/05/2017 07:53 PM, Adam Borowski wrote:
> Thus, here's a proposed solution: in unstable, there's now a bunch of
> packages that do such checking in preinst, and thus refuse (overridably) to
> even install such software.
>
> Currently this includes:
> * sse2: i386 (inc. hurd-i386, kfreebsd-i38
On Sat, 05 Aug 2017 21:20:37 +0200, Ole Streicher wrote:
> > So far I've seen mostly voices from people working in teams in this
> > thread who are in favour of dropping the required Uploaders field.
> So, if you want to count votes: I am working in teams (mainly Debian
> Astro), and I would favou
On Sat, Aug 05, 2017 at 10:04:28PM +0200, Philipp Kern wrote:
> On 08/05/2017 07:53 PM, Adam Borowski wrote:
> > Thus, here's a proposed solution: in unstable, there's now a bunch of
> > packages that do such checking in preinst, and thus refuse (overridably) to
> > even install such software.
> >
On 08/05/2017 10:04 PM, Philipp Kern wrote:
> On 08/05/2017 07:53 PM, Adam Borowski wrote:
>> Thus, here's a proposed solution: in unstable, there's now a bunch of
>> packages that do such checking in preinst, and thus refuse (overridably) to
>> even install such software.
>>
>> Currently this incl
Package: wnpp
Severity: wishlist
Owner: =?utf-8?b?WWFvIFdlaSAo6a2P6YqY5bu3KQ==?=
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
* Package name: fonts-alegreya-sans
Version : 2.001
Upstream Author : Juan del Peral
* URL : http://www.huertatipografica.com/en/fonts/ale
On Sat, Aug 05, 2017 at 07:53:02PM +0200, Adam Borowski wrote:
> Thus, here's a proposed solution: in unstable, there's now a bunch of
> packages that do such checking in preinst, and thus refuse (overridably) to
> even install such software.
[...]
A big issue here is that install-time is differe
Package: wnpp
Severity: wishlist
Owner: Apollon Oikonomopoulos
* Package name: trapperkeeper-scheduler-clojure
Version : 0.7.1
Upstream Author : Puppet Labs Inc
* URL : http://github.com/puppetlabs/trapperkeeper-scheduler
* License : Apache-2.0
Programming La
Package: wnpp
Severity: wishlist
Owner: =?utf-8?b?WWFvIFdlaSAo6a2P6YqY5bu3KQ==?=
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
* Package name: ufolib
Version : 2.1.0
Upstream Author : Unified Font Object
* URL : https://github.com/unified-font-object/ufoLib
* Licens
On Sat, Aug 05, 2017 at 11:50:42PM +0200, Guus Sliepen wrote:
> On Sat, Aug 05, 2017 at 07:53:02PM +0200, Adam Borowski wrote:
>
> > Thus, here's a proposed solution: in unstable, there's now a bunch of
> > packages that do such checking in preinst, and thus refuse (overridably) to
> > even instal
Tobias Frost writes:
> Am Donnerstag, den 03.08.2017, 11:58 -0700 schrieb Russ Allbery:
>> Or track MIA teams, which in a lot of ways is a much easier problem,
>> and seems like a worthwhile problem to solve anyway.
> No, because with a $TEAM you have to expand it to $TEAM_MEMBERS and
> check th
Package: wnpp
Owner: Valerie R Young
Severity: wishlist
* Package name: fortune-anarchism
Version : 1.2
Upstream Author : none
* URL : https://notabug.org/PangolinTurtle/BLAG-fortune
* License : public domain
Programming Lang: text
Description : anarchi
Ole Streicher writes:
> So, if you want to count votes: I am working in teams (mainly Debian
> Astro), and I would favour keeping it -- exactly for the reasons Adrian
> wrote: In Debian Astro, most packages are practically maintained by
> a single person, who should also feel responsible.
It's
Package: wnpp
Owner: Lev Lamberov
Severity: wishlist
* Package name: browse-kill-ring-el
Version : 2.0.0
Upstream Author : Colin Watson (original author)
Andrew Burgess (current maintainer)
Toon Claes (current maintainer)
> Upstream Author : Colin Watson (original author)
Sorry, a mistake. The original author is Colin Walters
.
Regards,
Lev Lamberov
> Upstream Author : Colin Watson (original author)
Sorry, a mistake. The original author is Colin Walters
.
Regards,
Lev Lamberov
36 matches
Mail list logo
