Re: Pre-Depends: init-system-helpers

Am 2014-11-17 18:07, schrieb Anthony Towns: BTW, it occured to me that it seems like a wart that update-rc.d doesn't respect policy-rc.d -- as it stands, policy-rc.d can prevent a service from (re)starting during install/upgrade, but it'll still start on the next boot. Is that just something t

PoC: cross-init-bridge

Hi there, (CC Steve Langsek, since he's maintainer/developer (?) of Upstart.) (I'm not on the debian-devel list, so please use reply to all.) People, especially in the TC, have criticized that there are different protocols for systemd and upstart to specify things such as notifications and/or soc

Re: PoC: cross-init-bridge

[Petter Reinholdtsen] > Have you consider the /lib/init/init-d-script approach now available > in unstable when considering how hard it is to maintain init.d > scripts? It allow package maintainers to only store the package > specific parts in their init.d scripts, and offload the complete > imple

Re: how to remove libsystemd0 from a live-running debian desktop system

Am 16.02.2015 um 02:54 schrieb Luke Kenneth Casson Leighton: http://lkcl.net/reports/removing_systemd_from_debian/ It's funny that when Wheezy (not Jessie!) came out, nobody complained that libsystemd-login0 (which is now part of libsystemd0) was as a dependency of dbus, so it is probably alrea

Re: RFH: dropbear initramfs support

On 06/27/2015 02:19 PM, Guilhem Moulin wrote: > Alright, that's it :-) The changelog is pretty heavy because I also > lintian-cleaned and modernized (using dh_* tools) the packages, as well as > fixed most bugs: > [...] > + Bring down interfaces and flush network configuration before existing

Re: RFH: dropbear initramfs support

Thanks for your quick reply! On 06/27/2015 05:01 PM, Guilhem Moulin wrote: > On Sat, 27 Jun 2015 at 16:20:56 +0200, Christian Seiler wrote: >> On 06/27/2015 02:19 PM, Guilhem Moulin wrote: >>> Alright, that's it :-) The changelog is pretty heavy because I also >>>

Re: RFH: dropbear initramfs support

On 06/27/2015 07:03 PM, Guilhem Moulin wrote: > On Sat, 27 Jun 2015 at 17:29:52 +0200, Christian Seiler wrote: >> As I said: the majority use case for dropbear in initramfs will not be >> these kinds of setups, so I think the new behavior should be the >> default setti

Re: Bug#790933: ITP: drive - Google Drive tool

On 07/05/2015 09:15 AM, Jackson Doak wrote: > It might be possible to rename the binary and symlink "drive" to it, which > would allow you to give the binary name over easier Personally, I think it would be best not to reserve such a generic name 'drive' for such a specific service. There could ea

Re: Bug#790933: ITP: drive - Google Drive tool

On 07/05/2015 10:46 PM, Tomas Pospisek wrote: > Am 05.07.2015 um 09:15 schrieb Jackson Doak: >> It might be possible to rename the binary and symlink "drive" to it, >> which would allow you to give the binary name over easier > > > Top-posting in a thread breaks the flow of the messages - as you

Re: Bug#790933: ITP: drive - Google Drive tool

On 07/06/2015 10:54 AM, Jonathan Dowland wrote: > On Sun, Jul 05, 2015 at 01:16:02PM +0200, Christian Seiler wrote: >> A good example for this is the open(1) command: way back when Linux was >> still in its infancy, somebody decided it would be a good idea to have >> a comman

Re: Bug#790933: ITP: drive - Google Drive tool

On 07/06/2015 10:58 AM, Jonathan Dowland wrote: > On Sun, Jul 05, 2015 at 01:16:02PM +0200, Christian Seiler wrote: >> [1] Suggestion: 'gdrive', if that's not already taken by something e.g. >> GLib/Gtk+-based (I haven't checked). > > Oh snap :) I did an

Re: Installer of Debian Stable allows to use btrfs for /, does it mean it's mature enough to use safely?

Am 2016-07-10 16:10, schrieb Marc Haber: I have severe allocation issues in btrfs with recent kernels and recent btrfs-tools when using thousands of snapshots. All the community had to offer was "well, try to restrict yourself to at most a few hundred snapshots". btrfs rebalance brings the whole

Re: sybase license and openWatcom DFSGness

On 08/01/2016 12:56 PM, Gianfranco Costamagna wrote: > We are not allowed to touch SeaBIOS for licence reasons. Not our decision. Maybe I don't quite understand what VirtualBox upstream meant by this sentence, but if the SeaBIOS license does not allow modification, then it would not be DFSG-free,

Re: Bug#833388: ITP: metaphlan2 -- Metagenomic Phylogenetic Analysis

On 08/03/2016 09:00 PM, Andreas Tille wrote: > 2b) Do the conversion of the format in postinst at the expense > of users time which is acceptable since the package usually > unpacks on high performance machines and not so many > installations which means bandwidth an

Re: Beware of leftover gpg-agent processes

On 08/05/2016 06:08 PM, Ian Jackson wrote: > Could we not have gpg2 not only automatically launch the agent, but > also automatically terminate it. This would provide the same UI and > same persistence properties as gpg1. Full ACK here, with the slight modification that the agent should only comm

Re: use long keyid-format in gpg.conf (Re: Key collisions in the wild

On 08/10/2016 03:19 PM, Samuel Thibault wrote: > Ian Jackson, on Wed 10 Aug 2016 13:45:05 +0100, wrote: >> Adam D. Barratt writes ("Re: use long keyid-format in gpg.conf (Re: Key >> collisions in the wild"): >>> [explanation] >> >> Thanks. >> >> I don't know what side of this (one) line such a pro

Re: use long keyid-format in gpg.conf (Re: Key collisions in the wild

On 08/10/2016 03:44 PM, Samuel Thibault wrote: > Christian Seiler, on Wed 10 Aug 2016 15:37:43 +0200, wrote: >> On 08/10/2016 03:19 PM, Samuel Thibault wrote: >>> Ian Jackson, on Wed 10 Aug 2016 13:45:05 +0100, wrote: >>>> Adam D. Barratt writes ("Re: use lon

Alternative solution (was: Re: Network access during build)

On 09/07/2016 07:17 AM, Vincent Bernat wrote: > One of the package that I maintain (python-asyncssh) makes a DNS request > during build and expects it to fail. Since Policy 4.9 forbids network > access (in a rather confusing wording "may not"), I got this serious > bug: > https://bugs.debian.org/c

Re: Alternative solution

On 09/07/2016 07:43 AM, Christian Seiler wrote: > However, instead of disabling the test via a patch, [...] Yet another solution would be to upstream a patch that adds the @unittest.skipIf(os.getenv('TESTS_NO_NETWORK_ACCESS') == '1', 'No network

Re: Porter roll call for Debian Stretch

On 09/21/2016 08:41 AM, Riku Voipio wrote: > AFAIK Address space randomizing is not really helpful on 32 bit > architectures - there is just not that many places to randomize to[1]. Well, sure, but there's still a huge difference in an explot with 100% reliability, or an exploit that will just cr

Re: Confused by autoremoval

On 10/02/2016 05:54 PM, Nikolaus Rath wrote: > Can someone explain to me why (according to the email that I've just > received) python-llfuse 1.1.1+dfsg-3 is marked for autoremoval from > testing on 2016-10-24? Probably , see the thread [1] from earlier this weekend

Re: package builds crashing under fakeroot

On 10/03/2016 04:50 PM, Alastair McKinstry wrote: > In OpenMPI 2.0, Michael Banck discovered that some of the packages that > failed were doing so as openmpi no longer works under fakeroot. > > Upstream (Gilles Gouaillaerdet) point out: > > from |validate_cred| in > |opal/mca/pmix/pmix112

Re: [Pkg-dns-devel] Bug#833309: "Browserified" stuff (knot-resolver-module-http: please package embedded epoch.js separately)

On 10/13/2016 08:03 AM, Mike Hommey wrote: > On Thu, Oct 13, 2016 at 05:48:00AM +, Niels Thykier wrote: >> W. Martin Borgert: >>> On 2016-10-12 21:41, Vincent Bernat wrote: ❦ 12 octobre 2016 18:54 CEST, Martín Ferrari : > I had always understood that rebuilding from source was a hard

Re: Package name conflict question

On 10/16/2016 10:07 AM, Alec Leamas wrote: > On 16/10/16 09:35, SZ Lin (林上智) wrote: >> I want to package python library - *uritemplate* [1]; however, I found >> that there is a same name package with similar function in Debian >> archive [3]. > >> Do you have any suggestion on it ? > > What abou

Re: Bug#841196: ITP: node-os-homedir -- Node.js 4 `os.homedir()` ponyfill

On 10/18/2016 05:29 PM, Pirate Praveen wrote: > On Tuesday 18 October 2016 08:27 PM, Lars Wirzenius wrote: >> This is so wrong, I would like to ask that this package not be allowed >> into Debian until it's fixed. > > I agree this could be marked RC and stopped from going to a stable > release. Bu

Re: Keysafe dynamic UID

On 10/24/2016 12:42 AM, Colin Watson wrote: > On Sat, Oct 22, 2016 at 02:57:23PM -0700, Sean Whitton wrote: >> I am packaging Keysafe,[1] and the binary package keysafe-server needs >> to create a new system user with a dynamically allocated UID. >> >> I am using the username 'keysafe'. I do not a

Re: Keysafe dynamic UID

On 10/24/2016 09:12 AM, Tollef Fog Heen wrote: > I'd prefer if user creation was just done declaratively and then we > could scan the archive. If we have a manually-maintained list, it will > get out of sync with reality pretty quickly. Doing this declaratively would definitely be the ideal solut

Re: openssl transition

On 10/29/2016 09:27 PM, Michael Meskes wrote: >> - The parallel use of release 1.0 and 1.1 will not be pursued? >> >> - Why is the transition started with 0 (zero) good packages (from > 552)? >> ... > > May I add one more, and actually pretty pressing question? How are we > supposed to upload "fi

Re: openssl transition

On 10/30/2016 11:03 AM, Michael Meskes wrote: > On Sat, Oct 29, 2016 at 10:04:21PM +0200, Christian Seiler wrote: >> Well, ideally it'll compile with both OpenSSL 1.0.2 and 1.1 and >> therefore be binNMU-able. (This has the advantage that such a >> patch is much more

Re: Lots and lots of tiny node.js packages

On 11/03/2016 09:37 PM, Bernd Zeimetz wrote: > On 11/02/2016 11:59 AM, Scott Leggett wrote: >> Actually, node is in a league of its own in this regard: >> >> http://www.modulecounts.com/ > > 492 new modules per day? are we sure we even want to start to package > something like that!??? I don't th

Bug#805268: Bug #805268: ITA: syslinux -- collection of bootloaders (DOS FAT and NTFS bootloader)

X-Debbugs-Cc: debian-devel@lists.debian.org Control: owner -1 ! Control: retitle -1 ITA: syslinux -- collection of bootloaders (DOS FAT and NTFS bootloader) On Mon, 16 Nov 2015 08:29:30 + Mattia Rizzolo wrote: > Some information about this package: > > Homepage: http://www.syslinux.org/ > P

Re: libc recently more aggressive about pthread locks in stable ?

On 11/05/2016 08:13 PM, Ian Jackson wrote: > I have just been debugging a ghostscript segfault on jessie amd64. > > Looking at the code, I think that gs in jessie is plainly violating > the rules about the use of pthread locks. On my partner's machine, > this makes it segfault on termination (wit

Re: More 5 november in the release schedule

On 11/06/2016 11:59 AM, Marc Haber wrote: > On Sun, 06 Nov 2016 09:38:00 +, Niels Thykier > wrote: >> Marc Haber: >>> On Sat, 5 Nov 2016 13:46:16 +0100, Sebastiaan Couwenberg >>> wrote: [2017-Jan-05] Soft freeze (no new packages, no re-entry, 10-day migrations) >>> >>>

Re: More 5 november in the release schedule

On 11/08/2016 08:31 AM, Scott Kitterman wrote: > On Tuesday, November 08, 2016 06:19:36 PM Brian May wrote: >> Christian Seiler writes: >>> Why? Any package currently in testing still has time to enter >>> (until roughly end of this year), so it's not like there is

Re: Build a sort-of-systemd-dependent package on kfreebsd

> However, my need is to actually *remove* some files from e. g., > debian/install since they are not built on kfreebsd. How could I do > this? cat > debian/$FOO.install <

Re: More 5 november in the release schedule

On 11/08/2016 08:47 PM, Adrian Bunk wrote: > On Tue, Nov 08, 2016 at 02:31:04AM -0500, Scott Kitterman wrote: >> On Tuesday, November 08, 2016 06:19:36 PM Brian May wrote: >>> Christian Seiler writes: >>>> Why? Any package currently in testing still has time to en

Re: missing -dbgsym packages on uploads by maintainer(s)

On 11/12/2016 08:10 AM, Andrey Rahmatullin wrote: > On Sat, Nov 12, 2016 at 12:58:13AM +0100, Adam Borowski wrote: >>> What stops us from throwing away .debs from maintainers starting tomorrow? >> >> The machinery for arch:all binaries is still incomplete: > Fine, what stops us from throwing away a

Re: [Letsencrypt-devel] Certbot in Debian Stretch

On 11/25/2016 10:34 AM, Thijs Kinkhorst wrote: > On Thu, November 24, 2016 22:28, Harlan Lieberman-Berg wrote: >> On November 24, 2016 11:59:46 AM EST, James Cloos >> wrote: >>> The jessie and jessie-backports releases of certbot have not, in >>> general, been usable. There have been usable windo

Re: Certbot in Debian Stretch

On 11/22/2016 02:40 AM, Peter Eckersley wrote: > 1. Leave Certbot out of the Debian Stretch release, and rely on > backports as the recommended way to run Certbot on Debian. That's what we > currently do with Jessie: Note that per backports rules, $RELEASE_N-backports must track $RELEASE_N_PLUS_1,

Re: [Letsencrypt-devel] Certbot in Debian Stretch

On 11/25/2016 12:45 PM, Christian Seiler wrote: > On 11/25/2016 10:34 AM, Thijs Kinkhorst wrote: >> On Thu, November 24, 2016 22:28, Harlan Lieberman-Berg wrote: >>> On November 24, 2016 11:59:46 AM EST, James Cloos >>> wrote: >>>> The jessie and jessie-bac

Bug#846237: ITP: ondir -- Automate tasks specific to certain directories in the shell

(Forwarding because I forgot to Cc debian-devel@.) Package: wnpp Owner: Christian Seiler Severity: wishlist * Package name: ondir Version : 0.2.3+git [*] Upstream Author : Alec Thomas * URL : http://swapoff.org/ondir.html * License : GPL-2 Programming Lang

Re: Bug#846237: ITP: ondir -- Automate tasks specific to certain directories in the shell

On 11/29/2016 04:23 PM, Julian Taylor wrote: > On 11/29/2016 03:41 PM, Christian Seiler wrote: >> (Forwarding because I forgot to Cc debian-devel@.) >> >> ondir is a small program to automate tasks specific to certain >> directories. It works by executing scripts in di

Re: Bug#846237: ITP: ondir -- Automate tasks specific to certain directories in the shell

On 11/29/2016 05:25 PM, Guus Sliepen wrote: > On Tue, Nov 29, 2016 at 03:41:29PM +0100, Christian Seiler wrote: > >> * Package name: ondir >> Version : 0.2.3+git [*] >> Upstream Author : Alec Thomas >> * URL : http://swapoff.org/ondir.htm

Re: Bug#846237: ITP: ondir -- Automate tasks specific to certain directories in the shell

On 11/29/2016 06:01 PM, Christian Seiler wrote: > On 11/29/2016 05:25 PM, Guus Sliepen wrote: >> On Tue, Nov 29, 2016 at 03:41:29PM +0100, Christian Seiler wrote: >> >>> * Package name: ondir >>> Version : 0.2.3+git [*] >>> Upstream Author

Re: [Letsencrypt-devel] Certbot in Debian Stretch

On 11/30/2016 02:33 PM, Virgo Pärna wrote: > On Fri, 25 Nov 2016 15:41:45 +0100, Christian Seiler > wrote: >> >> is not an issue (it works fine), but I had modified the cron job to >> pass --renew-hook and --post-hook to certbot. (As far as I can tell, >> there&

Re: [Letsencrypt-devel] Certbot in Debian Stretch

On 11/30/2016 10:12 PM, Peter Eckersley wrote: > On Wed, Nov 30, 2016 at 04:19:40PM +0100, Christian Seiler wrote: >> On 11/30/2016 02:33 PM, Virgo Pärna wrote: >>> On Fri, 25 Nov 2016 15:41:45 +0100, Christian Seiler >>> wrote: >>>> >>>> is n

Re: Bug#846366: ITP: bcc -- Command line tools for BPF Compiler Collection (BCC)

On 11/30/2016 10:32 PM, Karsten Merker wrote: > On Thu, Dec 01, 2016 at 12:56:14AM +0530, Ritesh Raj Sarraf wrote: >> On Wed, 2016-11-30 at 20:05 +0100, Karsten Merker wrote: >>> bcc is a package (and executable) name that is already in use for >>> another program in Debian. From https://packages.d

Re: Bug#847066: ITP: node-stream-shift -- Returns the next buffer/object in a stream's readable queue

On 12/05/2016 11:08 AM, Pirate Praveen wrote: > Package: wnpp > Severity: wishlist > Owner: Pirate Praveen > X-Debbugs-CC: debian-devel@lists.debian.org > > * Package name: node-stream-shift > Version : 1.0.0 > Upstream Author : Mathias Buus (@mafintosh) > * URL : http

Re: Bug#847066: ITP: node-stream-shift -- Returns the next buffer/object in a stream's readable queue

Control: merge 847066 847053 On 12/05/2016 02:03 PM, Pirate Praveen wrote: > On 2016, ഡിസംബർ 5 5:50:41 PM IST, Christian Seiler wrote: >> This appears to be a duplicate of https://bugs.debian.org/847053 > > I tried resending from a different address as I did not receive a >

Re: armel after Stretch

On 12/09/2016 01:53 AM, Ben Hutchings wrote: > On Thu, 2016-12-08 at 23:12 +0100, Christoph Biedl wrote: >> Roger Shimizu wrote... >> >>> I'm ARM porter on armel/marvell (orion5x/kirkwood). >>> Stretch will be frozen and released soon, which makes me bit depressed, >>> because it means armel will

Re: Bug#847749: ITP: node-user-home -- Get the path to the user home directory

On 12/11/2016 06:29 PM, Sruthi Chandran wrote: > On 12/11/2016 06:18 PM, Guus Sliepen wrote: >> Isn't s/user-home/os-homedir/ not enough? In any case, maybe you should >> try to get upstream to switch to os-homedir instead. > os-homedir is not packaged, we have been patching that with os.homedir. >

Re: Bug#847749: ITP: node-user-home -- Get the path to the user home directory

On 12/11/2016 06:52 PM, Christian Seiler wrote: > I've attached an updated use-os-homedir.patch that does this (including > the removal of the require.resolve() line above), And I just noticed that I forgot a semicolon after a line (not critical, because javascript doesn't

Re: Bug#847749: ITP: node-user-home -- Get the path to the user home directory

On 12/11/2016 07:57 PM, Sruthi Chandran wrote: > On 12/12/2016 12:20 AM, Sruthi Chandran wrote: >> On 12/11/2016 11:30 PM, Christian Seiler wrote: >>>> I've attached an updated use-os-homedir.patch that does this (including >>>> the removal of the require.

Re: Bug#847749: ITP: node-user-home -- Get the path to the user home directory

On 12/12/2016 04:22 PM, Holger Levsen wrote: > On Mon, Dec 12, 2016 at 04:08:15PM +0100, Lars Wirzenius wrote: >> On Mon, Dec 12, 2016 at 11:56:53AM -0300, Fernando Toledo wrote: >>> A package to get user home path ? >>> The world is dying... >> We've had a number of discussions about nodejs's appr

Re: Getting DEB_HOST_MULTIARCH from maintscripts

On 12/15/2016 10:50 PM, Mathieu Parent (Debian) wrote: > I need to have access to $DEB_HOST_MULTIARCH in prerm and postinst to > create the appropriate symlink with update-alternatives. > > What is the best way to do this? Generate them from .in files at the appropriate time, resolving the variab

Re: Getting DEB_HOST_MULTIARCH from maintscripts

On 12/16/2016 05:03 AM, Mathieu Parent (Debian) wrote: > 2016-12-16 1:24 GMT+01:00 Christian Seiler : >> On 12/15/2016 10:50 PM, Mathieu Parent (Debian) wrote: >>> I need to have access to $DEB_HOST_MULTIARCH in prerm and postinst to >>> create the appropriate symli

Re: depending on libssl1.0-dev, buildd fails to find it

On 12/17/2016 04:49 PM, Daniel Pocock wrote: > In my reSIProcate control[1] file, I included the following: > > Build-Depends: ... , libssl-dev (<< 1.1) | libssl1.0-dev (>= 1.0.0), ... > > pdebuild correctly builds it for sid with libssl1.0-dev from openssl1.0[2] > > In the buildd[3] report, it

Re: dput: Call for feedback: What should change? What should stay the same?

Hi there, On 12/28/2016 06:18 AM, Afif Elghraoui wrote: > but the dput > command from dput-ng does some spurious checks that fail and I've never > found worth the time to investigate. I only use dput-ng, but because of the extra checks that has already saved me from performing a wrong upload; the

Re: Can we kill net-tools, please?

On 12/29/2016 08:38 PM, Russ Allbery wrote: > It certainly doesn't provide a man page that doesn't start with a BNF > syntax description. The iproute2 documentation is awful. Ack. > Also, this is not at all easy to parse: > > # ip -o address > 1: loinet 127.0.0.1/8 scope host lo\ vali

Re: compression support in kmod

On 12/29/2016 11:47 PM, Christoph Biedl wrote: > Eduard Bloch wrote... > >> I volunteer as test subject for that experiment. I would appreciate even >> small steps, considering the current laptop in front of me with average >> magnetic HDD. Over a minute boot time, which is insane and IMHO mostly

Re: Bug#850255: ITP: node-is-retry-allowed -- My prime module

Hi there, Let me nitpick a bit: ;-) On 01/05/2017 12:52 PM, saurabhagra...@disroot.org wrote: > * URL : https://github.com/floatdrop/is-retry-allowed#readme > Description : My prime module The official package description appears to be: "Is retry allowed for Error?" And while

Re: Bug#850255: ITP: node-is-retry-allowed -- My prime module

On 01/05/2017 01:18 PM, Martin Bagge / brother wrote: > On 2017-01-05 13:04, Christian Seiler wrote: >> The official package description appears to be: > >> "Is retry allowed for Error?" > >> And while that is still a bit vague, it does at least give an >

Hiding library packages from apt searches by default? (was: Re: Worthless node-* package descriptions in ITPs)

On 01/05/2017 02:06 PM, Jonas Smedegaard wrote: > Quoting Riku Voipio (2017-01-05 12:53:16) >> Vast majority of users would only install this via dependencies. It's >> hardly a node-specific problem that debian package searches output >> large amount of packages that are not useful unless you hap

Re: [Fwd: [Pkg-pascal-devel] Bug#472304: marked as done (fpc: doesn't link dynamically)]

On 01/05/2017 08:27 PM, Sean Whitton wrote: > On Wed, Jan 04, 2017 at 09:24:32AM +0800, Paul Wise wrote: >> The solution is simply a lower bus factor in all Debian services, >> including the BTS [...] > > Could you explain "lower bus factor" a bit more, please? https://en.wikipedia.org/wiki/Bus_f

Re: Bug#852451: ITP: rname -- invoke a program under a different name

On 01/24/2017 04:19 PM, Peter Pentchev wrote: > Package: wnpp > Severity: wishlist > Owner: Peter Pentchev > > * Package name: rname > Version : 1.0.2 > Upstream Author : Peter Pentchev > * URL : https://devel.ringlet.net/sysutils/rname/ > * License : BSD-2-cl

Re: lintian: shlib-read-write-env

On 01/31/2017 11:15 AM, Mathieu Malaterre wrote: > I'd like to discuss addition of a new lintian checks for > getenv/setenv/putenv used in shared libraries. Why getenv() though? It just reads the environment. >From what you link yourself: | The getenv and secure_getenv functions can be safely use

Re: lintian: shlib-read-write-env

On 01/31/2017 04:49 PM, Ben Hutchings wrote: > On Tue, 2017-01-31 at 14:23 +0100, Christian Seiler wrote: >> On 01/31/2017 11:15 AM, Mathieu Malaterre wrote: >>> I'd like to discuss addition of a new lintian checks for >>> getenv/setenv/putenv used in shared libr

Re: Help requested: Packages which FTBFS randomly

On 02/20/2017 11:05 AM, Jonathan Dowland wrote: > On Mon, Feb 20, 2017 at 01:57:52AM +0100, Adam Borowski wrote: >> * single-CPU machines have gone the way of the dodo. Even the crummiest >> machine I could find while dumpster-diving looking for a non-sse3 one >> already has HT and builds your

Re: Bug#858229: ITP: passh -- passh: a pass fork - stores, retrieves, generates, and synchronizes passwords securely.

On 03/20/2017 06:18 AM, Adrian Alves wrote: > Package: wnpp > Severity: wishlist > Owner: Adrian Alves > > * Package name: passh > Version : 1.7.1 > Upstream Author : Ivan Ariel Barrera Oro > * URL : https://github.com/HacKanCuBa/passh > * License : GPL-3 >

Re: Bug#858229: ITP: passh -- passh: a pass fork - stores, retrieves, generates, and synchronizes passwords securely.

Hi again, On 03/20/2017 07:43 AM, Christian Seiler wrote: > And while that shouldn't be part of the package description later on, > a short comment in the ITP why a fork was required would also be nice. > Did the original project just not want to merge this? What's the u

Rethinking dynamic linking a bit (was: Re: Depends/Recommends from libraries)

On 03/08/2017 11:33 PM, Adam Borowski wrote: > I'd like to discuss (and then propose to -policy) the following rule: > > # Libraries which don't provide a convenient means of conditionally loading > # at runtime (this includes most libraries for languages such as C), SHOULD > # NOT declare a "Depe

Re: Bug#860771: ITP: node-diffie-hellman -- pure js diffie-hellman

On 04/19/2017 11:36 PM, Bastien ROUCARIES wrote: > Package: wnpp > Severity: wishlist > Owner: ro...@debian.org > X-Debbugs-CC: debian-devel@lists.debian.org > > * Package name: node-diffie-hellman > Version : 5.0.2 > Upstream Author : Calvin Metcalf > * URL : https://g

Re: Bug#860771: ITP: node-diffie-hellman -- pure js diffie-hellman

On 04/20/2017 11:09 AM, Bastien ROUCARIES wrote: > I have planned to add a big fat warning about safety of > browserify-crypto. I am myself unease to use it but it is needed for > browserify. > > Do you prefer a README.debian per pure js crypto package ? Maybe also add something along the lines o

Re: policy for shipping sysctl.d snippets in packages?

On 04/24/2017 08:20 PM, Marc Haber wrote: > Or it was the other way round. I remember going through bizarre > contortions to set IPv6 ip_forwarding on jessie without > systemd-networkd supporting this "exotic" use case. Note that it took a _ton_ of iterations for systemd-networkd to converge on a

Re: policy for shipping sysctl.d snippets in packages?

On 04/25/2017 07:59 PM, Wouter Verhelst wrote: > In my experience as a user of some of those packages, it is intensely > annoying that a package upgrade suddenly changes some behaviour in ways > that I dislike and it's difficult to figure out what changed, because > the configuration is not in /etc

Re: policy for shipping sysctl.d snippets in packages?

On 05/01/2017 09:13 AM, Marc Haber wrote: > I find it already disturbing that we have diverged from "our" way in > systemd, which is probably the first package a local admin will be > exposed to. This is nothing new though. For example, DBus has had the /usr and /etc split since as far back as I c

Re: policy for shipping sysctl.d snippets in packages?

On 05/01/2017 01:02 PM, Marc Haber wrote: > On Mon, 1 May 2017 11:09:26 +0200, Christian Seiler > wrote: >> And as I said in other places in this thread: I personally >> think that the separate /usr <-> /etc scheme is much better >> than just storing everyth

Re: Bug#861639: ITP: node-elliptic -- fast elliptic curve cryptography in pure javascript

Hi there, On 05/02/2017 07:49 AM, Pirate Praveen wrote: > Package: wnpp > Severity: wishlist > Owner: Pirate Praveen > X-Debbugs-CC: debian-devel@lists.debian.org > > * Package name: node-elliptic > Version : 6.4.0 > Upstream Author : Fedor Indutny > * URL : https://

Re: Bug#861639: ITP: node-elliptic -- fast elliptic curve cryptography in pure javascript

On 05/02/2017 10:13 PM, Bastien ROUCARIES wrote: > On Tue, May 2, 2017 at 8:44 PM, Chris Lamb wrote: >> Christian Seiler wrote: >> >>> As with the other pure JS crypto package ITP here recently [1]: has >>> this library been designed with timing attacks in mi

Re: Too many Recommends (in particular on mail-transport-agent)

Hi there, Am 2017-06-06 15:55, schrieb Adam Borowski: pulseaudio: xfce4-pulseaudio-plugin * BAD: I want working sound, duh. I know there's a faction of people out there who absolutely despise PulseAudio, and that they constantly have problems with it. But, as a request collective to all of you

Re: Too many Recommends (in particular on mail-transport-agent)

Hi there, I think one of the main problems with Recommends: is not actually the dependencies of packages themselves (I think that most things in your list I disagree with, those Recommends: are fine in my eyes), but rather in the way they are handled in APT. Let me make a couple of points (some

Re: DEP 15: Reserved namespace for DD-approved non-maintainer changes

Hi Sean, Am 2017-06-07 22:56, schrieb Sean Whitton: I am hereby reserving DEP number 15 for my draft DEP, "Reserved namespaces for DD-approved non-maintainer changes". I'd like to suggest discussing this DEP on d-devel (which is the Reply-to for this e-mail). The canonical DEP text is at

Re: Too many Recommends (in particular on mail-transport-agent)

Am 2017-06-08 16:07, schrieb Johannes Schauer: Quoting Christian Seiler (2017-06-07 15:26:35) - You install package A, which Recommends: B, but you don't want B, notice that at the time, and either remove B afterwards, or install A with --no-install-recommends. But the

Re: DEP 15: Reserved namespace for DD-approved non-maintainer changes

On 06/11/2017 07:44 PM, Sean Whitton wrote: > Christian Seiler writes: > >> To me this looks like a very complicated technical solution >> to something that I've never encountered as a problem myself. > > Could you explain which parts of the proposal you f

Re: DEP 15: Reserved namespace for DD-approved non-maintainer changes

On 06/19/2017 05:37 PM, Sean Whitton wrote: > On Mon, Jun 19, 2017 at 08:56:14AM -0400, Jeremy Bicha wrote: >> On Mon, Jun 19, 2017 at 5:18 AM, Sean Whitton >> wrote: >>> Someone might contribute a fix in the form of a PR, and an uploader of >>> the package might review that fix and determine tha

Re: Debian built from non-Debian sources

On 07/16/2017 11:12 PM, Jonas Smedegaard wrote: > It was just an example, however, and my real question was generally what > governs code we distribute outside packages - i.e. our install images, > if Debian Policy covers only packages. I don't know if this is actually in Policy or not, but in m

Re: Running tests with xvfb

Hi, On 07/28/2017 10:46 PM, Jeff wrote: > I have a package whose tests crash X on my machine, which uses nouveau. > This makes testing rather inconvenient. > > Running the tests in a chroot with xvfb works, but takes an age (i.e. a > couple of minutes) to set up the chroot. This is also not condu

Re: Bits from the 10th Debian Groupware Meeting

Hi, On 08/03/2017 03:21 PM, Rainer Dorsch wrote: > thank you for all the links. My main question was why it is not listed at > all > in the groupware wiki, you could easily list nextcloud/owncloud in the > section > "Groupware projects not currently considered for inclusion in Debian". It's

Re: Bug#798476: Returning to the requirement that Uploaders: contain humans

On 08/03/2017 08:58 PM, Russ Allbery wrote: > Jonas Smedegaard writes: > >> Do the MIA team also track MIA teams? > >> My concern is that packages without maintainers may go unnoticed when >> none of its previously active maintainers were tracked individually. > >> For such detection of abando

Re: sse{2,3,4.2}, altivec, neon, ...

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

Re: Let's enable AppArmor by default (why not?)

On 08/06/2017 05:32 PM, intrigeri wrote: > Moritz Mühlenhoff: >> If one of those profiles relies on features which are not upstreamed >> on the kernel end, how's that handled? > > Rules that are not supported by the running kernel are silently > ignored, i.e. the operation is allowed. Is there at

Re: MBF for deprecating Python2 usage

On 08/05/2017 07:34 AM, Josh Triplett wrote: > Scott Kitterman wrote: >> Reintroducing /usr/bin/python as a python3 version risks their systems >> for no benefit (since all python3 stuff points to /usr/bin/python3 and >> works fine). Just let it go and don't bring it back. > > Agreed completely.

Re: MBF for deprecating Python2 usage

Hi Matthias, On 08/03/2017 11:57 PM, Matthias Klose wrote: > It might not be possible to drop Python2 for the next release, Even if all Python-related packages in Debian were compatible with Python3, I don't think it's a good idea to drop Python2 support in Buster, there are still far too many th

Re: Let's enable AppArmor by default (why not?)

On 08/09/2017 10:33 PM, intrigeri wrote: > Christian Seiler: >> On 08/06/2017 05:32 PM, intrigeri wrote: >>> Rules that are not supported by the running kernel are silently >>> ignored, i.e. the operation is allowed. > >> Is there at least a warning during the

Re: OpenSSL disables TLS 1.0 and 1.1

Hi, Am 2017-08-11 15:09, schrieb Sven Hartge: Unless it has been proven that TLS1.0 and TLS1.1 are as broken as SSL3, please keep the support for them enabled in OpenSSL, and just change the defaults in the application to only use TLS1.2 (unless changed by the administrator). I remember a ta

Re: Proposal: A new approach to differential debs

On 08/13/2017 07:11 PM, Peter Silva wrote: >> apt by default automatically deletes packages files after a successful >> install, > > I don't think it does that. The "apt" command line tool doesn't, but traditional "apt-get" does, as does "aptitude". This was documented in the release notes of Je

Re: Proposal: A new approach to differential debs

(Setting reply-to to debian-devel@ only as I don't think this should continue on debian-dpkg@ and deity@) On 08/14/2017 12:29 AM, Marvin Renich wrote: > * Christian Seiler [170813 13:19]: >> On 08/13/2017 07:11 PM, Peter Silva wrote: >>>> apt by default automatically de

A radically different proposal for differential updates

Hi there, I've come to believe that binary diff packages are not the best way of solving this issue. Intead I'd like to propse a radically different solution to this issue. The gist of it: instead of adding a format for how deltas work, I propose to introduce a new format for storing Debian packa

Re: MBF: Multi-Arch: same violations

Am 2017-08-28 09:14, schrieb Helmut Grohne: Here is the bug template: v v v v v Package: $1 Severity: important User: multiarch-de...@lists.alioth.debian.org Usertags: multiarch $1 is marked Multi-Arch: same, but fails to coinstall with itself on $2 and $3. You can find a failing installation l

Re: Removal of upstart integration

On 09/24/2017 01:32 AM, Thomas Goirand wrote: > On 09/13/2017 02:56 PM, Ian Jackson wrote: >> Alexandre Detiste writes ("Re: Removal of upstart integration"): >>> Please also sprinkle these maintainers scripts with some >>> >>> rmdir /etc/init --ignore-fail-on-non-empty >> >> That should be >> >

  1   2   >