Re: Bug#1035904: dpkg currently warning about merged-usr systems (revisited)

On May 17 2023, Andrea Pappacoda wrote: > Hi all, > > first of all thank you for this great thread. While I could feel some tension > while > reading it, it's completely normal and I've learned a lot. > > I have a question though: if /lib64/ld-linux-x86-64.so.2 is already a symlink > on >

Re: Automating signing of DKMS modules with machine owner key

On Aug 05 2020, Jeremy Stanley wrote: > On 2020-08-05 20:30:59 +0100 (+0100), Nikolaus Rath wrote: >> On Aug 04 2020, Jeremy Stanley wrote: >> > Okay, so for systems to which a malicious party may gain physical >> > access (or remote console access) t

Re: Automating signing of DKMS modules with machine owner key

On Aug 04 2020, Jeremy Stanley wrote: > Okay, so for systems to which a malicious party may gain physical > access (or remote console access) there's sort of a third risk this > addresses. A special case of the second risk really. *If* you're > also encrypting the filesystem on which that signing

Re: Heads up: persistent journal has been enabled in systemd

On Feb 05 2020, Scott Kitterman wrote: > On February 5, 2020 12:35:45 PM UTC, Ansgar wrote: >>On Wed, 2020-02-05 at 07:44 +, Scott Kitterman wrote: >>> Do syslog facilities really have to be addressed by number rather >>than name? That seems like a horrible interface. >> >>Currently yes.

Re: Adding security features

On Feb 05 2020, Anthony DeRobertis wrote: > On February 5, 2020 9:49:36 AM UTC, Nikolaus Rath wrote: >>On Feb 04 2020, Anthony DeRobertis wrote: >>> Google has at some point had results from >>> Gmail in the web search results (no idea if they currently do). >

Re: Adding security features

On Feb 04 2020, Anthony DeRobertis wrote: > Google has at some point had results from > Gmail in the web search results (no idea if they currently do). Would you have a reference for this please? Best, -Nikolaus -- GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F

Accepted s3ql 3.3.2+dfsg-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 20 Oct 2019 12:01:04 +0100 Source: s3ql Architecture: source Version: 3.3.2+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath Changed-By: Nikolaus Rath Changes: s3ql (3.3.2+dfsg-1) unstable; urgency

Re: Git Packaging Round 2: When to Salsa

On Sep 08 2019, Sam Hartman wrote: > Hopefully you will choose to monitor merge requests for your > repository. If not, turn off merge requests. Monitor *and respond to* might be a better phrasing..? Best, Nikolaus -- GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F

Accepted s3ql 3.3+dfsg-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 08 Sep 2019 15:58:56 +0100 Source: s3ql Architecture: source Version: 3.3+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath Changed-By: Nikolaus Rath Changes: s3ql (3.3+dfsg-1) unstable; urgency=medium

Accepted s3ql 3.2+dfsg-3 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 02 Aug 2019 11:22:40 +0200 Source: s3ql Binary: s3ql s3ql-dbg Architecture: source Version: 3.2+dfsg-3 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath Changed-By: Nikolaus Rath Description: s3ql

Accepted s3ql 3.2+dfsg-2 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 31 Jul 2019 11:29:32 +0200 Source: s3ql Binary: s3ql s3ql-dbg Architecture: source Version: 3.2+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath Changed-By: Nikolaus Rath Description: s3ql

Accepted s3ql 3.2+dfsg-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 17 Jul 2019 16:54:35 +0100 Source: s3ql Binary: s3ql s3ql-dbg Architecture: source Version: 3.2+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath Changed-By: Nikolaus Rath Description: s3ql

Re: dgit advocacy again (Re: Survey results: git packaging practices / repository format)

On Jul 03 2019, Andreas Tille wrote: >> > That's the case for me. I need to admit that I did not used dgit. The >> > reason is that I'm working in teams who all have Git repositories on >> > Salsa that more or less are following what was described in the Perl >> > team policy. I live under the

Re: Survey: git packaging practices / repository format

On May 29 2019, Sam Hartman wrote: > I'm certainly going to look at dck-buildpackage now, because what he > describes is a workflow I'd like to be using within Debian. > > For some projects I want to ignore orig tarballs as much as I can. I'm > happy with native packages, or 3.0 quilt with

Accepted s3ql 3.1+dfsg-2 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 10 Apr 2019 21:42:10 +0100 Source: s3ql Binary: s3ql s3ql-dbg Architecture: source Version: 3.1+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath Changed-By: Nikolaus Rath Description: s3ql

Accepted s3ql 3.1+dfsg-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 06 Apr 2019 16:28:05 +0100 Source: s3ql Binary: s3ql s3ql-dbg Architecture: source Version: 3.1+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath Changed-By: Nikolaus Rath Description: s3ql

Accepted python-llfuse 1.3.6+dfsg-1 (source) into unstable

Maintainer: Nikolaus Rath Changed-By: Nikolaus Rath Description: python-llfuse - Python bindings for the low-level FUSE API python-llfuse-dbg - Python bindings for the low-level FUSE API (debugging symbols) python-llfuse-doc - Python bindings for the low-level FUSE API (documentation) python3

Accepted s3ql 3.0+dfsg-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 09 Feb 2019 10:09:05 + Source: s3ql Binary: s3ql s3ql-dbg Architecture: source Version: 3.0+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath Changed-By: Nikolaus Rath Description: s3ql

Accepted python-dugong 3.7.4+dfsg-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 19 Jan 2019 15:45:15 + Source: python-dugong Binary: python3-dugong python-dugong-doc Architecture: source Version: 3.7.4+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath Changed-By: Nikolaus Rath

Re: Bits from the DPL (December 2018)

On Jan 01 2019, Chris Lamb wrote: > Hi Nikolaus, > >> > * Followed-up on progress regarding potential new "Member Benefits" >> >[9] and ensured that some previously-promised reports for events >> >funded by Debian ended up appearing on Planet [10]. >> > >> >I also provided solicited

Re: fuse -> fuse3

On Dec 25 2018, "Theodore Y. Ts'o" wrote: > On Fri, Dec 21, 2018 at 11:03:34PM +0100, Oibaf wrote: >> The package fuse3 is available since awhile in sid/buster. >> Their users however are still using old fuse (v2), e.g. sshfs-fuse. >> According to this: >>

Re: Bits from the DPL (December 2018)

On Dec 31 2018, Chris Lamb wrote: > * Followed-up on progress regarding potential new "Member Benefits" >[9] and ensured that some previously-promised reports for events >funded by Debian ended up appearing on Planet [10]. > >I also provided solicited (!) advice to a few other

Accepted s3ql 2.33+dfsg-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 28 Dec 2018 20:04:28 + Source: s3ql Binary: s3ql s3ql-dbg Architecture: source Version: 2.33+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath Changed-By: Nikolaus Rath Description: s3ql

Accepted s3ql 2.32+dfsg-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 06 Nov 2018 19:40:48 + Source: s3ql Binary: s3ql s3ql-dbg Architecture: source Version: 2.32+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath Changed-By: Nikolaus Rath Description: s3ql

Bug#912752: ITP: pyfuse3 -- Python 3 bindings for libfuse 3 using asynchronous I/O

Package: wnpp Severity: wishlist Owner: Nikolaus Rath * Package name: pyfuse3 Version : 1.1 Upstream Author : Nikolaus Rath * URL : https://github.com/libfuse/pyfuse3 * License : LGPL Programming Lang: Python Description : Python 3 bindings

Accepted s3ql 2.30+dfsg-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 02 Sep 2018 12:48:32 +0100 Source: s3ql Binary: s3ql s3ql-dbg Architecture: source Version: 2.30+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath Changed-By: Nikolaus Rath Description: s3ql

Accepted python-llfuse 1.3.5+dfsg-1 (source) into unstable

Maintainer: Nikolaus Rath Changed-By: Nikolaus Rath Description: python-llfuse - Python bindings for the low-level FUSE API python-llfuse-dbg - Python bindings for the low-level FUSE API (debugging symbols) python-llfuse-doc - Python bindings for the low-level FUSE API (documentation) python3

Accepted s3ql 2.29+dfsg-2 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 05 Aug 2018 11:13:54 +0100 Source: s3ql Binary: s3ql s3ql-dbg Architecture: source Version: 2.29+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath Changed-By: Nikolaus Rath Description: s3ql

Re: Should the weboob package stay in Debian?

On Jul 26 2018, Adam Borowski wrote: >> Promoting objectification of half of the world's population doesn't >> count as constructive social interaction in my understanding. > > That "objectification" is an invention of your particular religion[1]. I honestly don't see any connection to religion

Accepted python-llfuse 1.3.3+dfsg-4 (source) into unstable

Maintainer: Nikolaus Rath Changed-By: Nikolaus Rath Description: python-llfuse - Python bindings for the low-level FUSE API python-llfuse-dbg - Python bindings for the low-level FUSE API (debugging symbols) python-llfuse-doc - Python bindings for the low-level FUSE API (documentation) python3

How to help getting libfuse updated?

control: retitle 840075 "Please package libfuse 3" thanks Hi Laszlo, What kind of help would be needed to move this forward? libfuse 3 has been released in 2016, and this bug has been open for even longer (giving advance notice and referring to a pre-release for testing) with no update. It

Accepted s3ql 2.28+dfsg-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 14 Jun 2018 12:19:15 +0100 Source: s3ql Binary: s3ql s3ql-dbg Architecture: source Version: 2.28+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath Changed-By: Nikolaus Rath Description: s3ql

Accepted s3ql 2.27.1+dfsg-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 09 Jun 2018 12:05:27 +0100 Source: s3ql Binary: s3ql s3ql-dbg Architecture: source Version: 2.27.1+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath Changed-By: Nikolaus Rath Description: s3ql

Accepted python-dugong 3.7.3+dfsg-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 29 Apr 2018 19:09:23 +0100 Source: python-dugong Binary: python3-dugong python-dugong-doc Architecture: source Version: 3.7.3+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath <nikol...@rath.org> C

Accepted s3ql 2.26+dfsg-4 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 07 Apr 2018 20:05:17 +0100 Source: s3ql Binary: s3ql s3ql-dbg Architecture: source Version: 2.26+dfsg-4 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath <nikol...@rath.org> Changed-By: Nikolaus Rath

Accepted s3ql 2.26+dfsg-3 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 04 Apr 2018 14:55:21 +0100 Source: s3ql Binary: s3ql s3ql-dbg Architecture: source Version: 2.26+dfsg-3 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath <nikol...@rath.org> Changed-By: Nikolaus Rath

Accepted s3ql 2.26+dfsg-2 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 04 Apr 2018 09:51:16 +0100 Source: s3ql Binary: s3ql s3ql-dbg Architecture: source Version: 2.26+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath <nikol...@rath.org> Changed-By: Nikolaus Rath

Accepted python-llfuse 1.3.3+dfsg-3 (source) into unstable

Maintainer: Nikolaus Rath <nikol...@rath.org> Changed-By: Nikolaus Rath <nikol...@rath.org> Description: python-llfuse - Python bindings for the low-level FUSE API python-llfuse-dbg - Python bindings for the low-level FUSE API (debugging symbols) python-llfuse-doc - Python bindings

Accepted python-dugong 3.7.2+dfsg-3 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 04 Apr 2018 10:05:59 +0100 Source: python-dugong Binary: python3-dugong python-dugong-doc Architecture: source Version: 3.7.2+dfsg-3 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath <nikol...@rath.org> C

Accepted python-dugong 3.7.2+dfsg-2 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 04 Apr 2018 09:53:12 +0100 Source: python-dugong Binary: python3-dugong python-dugong-doc Architecture: source Version: 3.7.2+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath <nikol...@rath.org> C

Accepted python-llfuse 1.3.3+dfsg-2 (source) into unstable

Maintainer: Nikolaus Rath <nikol...@rath.org> Changed-By: Nikolaus Rath <nikol...@rath.org> Description: python-llfuse - Python bindings for the low-level FUSE API python-llfuse-dbg - Python bindings for the low-level FUSE API (debugging symbols) python-llfuse-doc - Python bindings

Accepted python-llfuse 1.3.3+dfsg-1 (source) into unstable

Maintainer: Nikolaus Rath <nikol...@rath.org> Changed-By: Nikolaus Rath <nikol...@rath.org> Description: python-llfuse - Python bindings for the low-level FUSE API python-llfuse-dbg - Python bindings for the low-level FUSE API (debugging symbols) python-llfuse-doc - Python bindings

Re: New lintian warning: vcs-deprecated-in-debian-infrastructure

On Mar 23 2018, Ben Finney wrote: >> You need online access to make use of the above information in any >> way. >> >> If you want to contact the maintainer you need internet access > > With the maintainer email address, I do not need internet access to > compose an email

Accepted s3ql 2.26+dfsg-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 04 Mar 2018 11:39:35 + Source: s3ql Binary: s3ql s3ql-dbg Architecture: source Version: 2.26+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath <nikol...@rath.org> Changed-By: Nikolaus Rath

Accepted python-dugong 3.7.2+dfsg-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 11 Feb 2018 16:09:49 + Source: python-dugong Binary: python3-dugong python-dugong-doc Architecture: source Version: 3.7.2+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath <nikol...@rath.org> C

Effect of build profiles

On Jan 11 2018, Johannes Schauer wrote: > We can check whether two binary packages built with a different set of > build profiles active are actually the same by using the tools from > the reproducible builds project. Now I'm mightily confused. What's the point of build

Accepted s3ql 2.25+dfsg-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 05 Jan 2018 12:05:16 +0100 Source: s3ql Binary: s3ql s3ql-dbg Architecture: source Version: 2.25+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath <nikol...@rath.org> Changed-By: Nikolaus Rath

Accepted python-llfuse 1.3.2+dfsg-2 (source) into unstable

Maintainer: Nikolaus Rath <nikol...@rath.org> Changed-By: Nikolaus Rath <nikol...@rath.org> Description: python-llfuse - Python bindings for the low-level FUSE API python-llfuse-dbg - Python bindings for the low-level FUSE API (debugging symbols) python-llfuse-doc - Python bindings

Accepted python-llfuse 1.3.2+dfsg-1 (source) into unstable

Maintainer: Nikolaus Rath <nikol...@rath.org> Changed-By: Nikolaus Rath <nikol...@rath.org> Description: python-llfuse - Python bindings for the low-level FUSE API python-llfuse-dbg - Python bindings for the low-level FUSE API (debugging symbols) python-llfuse-doc - Python bindings

Accepted s3ql 2.24+dfsg-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 04 Nov 2017 14:04:39 + Source: s3ql Binary: s3ql s3ql-dbg Architecture: source Version: 2.24+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath <nikol...@rath.org> Changed-By: Nikolaus Rath

Accepted python-llfuse 1.3+dfsg-3 (source) into unstable

Maintainer: Nikolaus Rath <nikol...@rath.org> Changed-By: Nikolaus Rath <nikol...@rath.org> Description: python-llfuse - Python bindings for the low-level FUSE API python-llfuse-dbg - Python bindings for the low-level FUSE API (debugging symbols) python-llfuse-doc - Python bindings for t

Accepted python-dugong 3.7.1+dfsg-2 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 01 Oct 2017 13:12:07 +0100 Source: python-dugong Binary: python3-dugong python-dugong-doc Architecture: source Version: 3.7.1+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath <nikol...@rath.org> C

Accepted python-llfuse 1.3+dfsg-2 (source) into unstable

Maintainer: Nikolaus Rath <nikol...@rath.org> Changed-By: Nikolaus Rath <nikol...@rath.org> Description: python-llfuse - Python bindings for the low-level FUSE API python-llfuse-dbg - Python bindings for the low-level FUSE API (debugging symbols) python-llfuse-doc - Python bindings for t

Accepted python-llfuse 1.3+dfsg-1 (source) into unstable

Maintainer: Nikolaus Rath <nikol...@rath.org> Changed-By: Nikolaus Rath <nikol...@rath.org> Description: python-llfuse - Python bindings for the low-level FUSE API python-llfuse-dbg - Python bindings for the low-level FUSE API (debugging symbols) python-llfuse-doc - Python bindings for t

Re: Whether remotely running software is considered "software" for Debian.

On Aug 28 2017, Andrey Rahmatullin wrote: > My position is that it should acceptable for a program in main to require > a non-free service, or data, or whatever, as long as that program itself > is free and running it doesn't compromise the freedom of the user. > contrib should

Accepted s3ql 2.23+dfsg-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 19 Aug 2017 14:38:51 +0200 Source: s3ql Binary: s3ql s3ql-dbg Architecture: source Version: 2.23+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath <nikol...@rath.org> Changed-By: Nikolaus Rath

Re: Embedded library copies - mergerfs

On Aug 07 2017, Antonio SJ Musumeci wrote: [libfuse] > There are secondary issues related to v2 being no longer maintained What makes you think so? I'm not adding new features, but it's definitely still being maintained. Best, -Nikolaus -- GPG Fingerprint: ED31 791B 2C5C

Re: Embedded library copies - mergerfs

On Aug 07 2017, Ben Finney wrote: > By your description, the upstream code doesn't do that. One obvious > workaround is to remove the embedded library in the Debian ‘mergerfs’ > package ‘clean’ target, patch the software to instead use Debian's > packaged ‘libfuse’ library,

Re: Naming of network devices - how to improve it in buster

On Jul 11 2017, Simon McVittie wrote: > On Tue, 11 Jul 2017 at 13:45:25 +0200, Bjørn Mork wrote: >> I got to ask: Why? We do not have stable names for e.g. disks. Why do >> we need it for network devices? > > We do have stable names for disks: look in /dev/disk/by-* and you'll

Re: Naming of network devices - how to improve it in buster

On Jul 11 2017, Michael Biebl wrote: > Am 11.07.2017 um 12:14 schrieb Guus Sliepen: >> Ok, it should be clear now that the new way of naming interfaces is not >> ideal, but the older ways weren't either. Let's have a look at what we >> want: >> >> - A simple name for systems

Accepted s3ql 2.22+dfsg-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 23 Jun 2017 09:53:10 -0700 Source: s3ql Binary: s3ql s3ql-dbg Architecture: source Version: 2.22+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath <nikol...@rath.org> Changed-By: Nikolaus Rath

Re: What HN would like to see in buster

On Jun 20 2017, Sean Whitton wrote: > While browsing the thread, I was struck by the number of requests for > tools and features that we already have -- things like checkinstall, > reportbug, dgit and continued support for sysvinit. > > I don't know how we could better

Accepted python-dugong 3.7.1+dfsg-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 15 Jun 2017 10:39:56 -0700 Source: python-dugong Binary: python3-dugong python-dugong-doc Architecture: source Version: 3.7.1+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath <nikol...@rath.org> C

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

On Jun 08 2017, Adrian Bunk wrote: > On Wed, Jun 07, 2017 at 03:26:35PM +0200, Christian Seiler wrote: >>... >> - 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

Re: Switch default installation image link?

On Jun 06 2017, Steve McIntyre wrote: > I'm *also* tempted to switch from the netinst to the first DVD image > instead - network connections have improved a lot. Why is that relevant? Is installing+downloading the DVD image faster than downloading netint + installing from

Re: A proposal for a tool to build local testing debs

On May 25 2017, Sean Whitton wrote: > Then in dgit-user(7), the SUMMARY would become > > SUMMARY >(These runes will be discussed later.) > >% dgit clone glibc jessie,-security >% cd glibc >% wget >

Re: When do we update the homepage to a modern design? (was Re: Moving away from (unsupportable) FusionForge on Alioth)

On May 15 2017, Adam Borowski wrote: >> https://www.debian.org/ > > Not that different from Gentoo's. What's the problem you're seeing? I think this is one of the those situations where if you don't see it yourself right away, you'll just have to take other people's word

Re: Moving away from (unsupportable) FusionForge on Alioth?

On May 15 2017, gregor herrmann wrote: > On Mon, 15 May 2017 14:43:56 +0200, Johannes Schauer wrote: > >> Quoting Jonathan Dowland (2017-05-15 10:25:30) >> > ^ how many of these are from teams (like pkg-gnome, at one point at least) >> > who want to switch to git but lack the

Re: "Ask HN: What do you want to see in Ubuntu 17.10?"

On Apr 08 2017, Wouter Verhelst wrote: >> - Airplane-mode Hotkey (especially hard apparently) >> - Volume Hotkeys >> - Brightness Hotkeys >> - Suspend/hibernate hotkeys > > These are all implemented by ACPI on modern hardware. You need to have > something that turns the ACPI

Re: "Ask HN: What do you want to see in Ubuntu 17.10?"

On Apr 06 2017, Gunnar Wolf <gw...@debian.org> wrote: > Nikolaus Rath dijo [Wed, Apr 05, 2017 at 03:18:57PM -0700]: >> >> I have a very different perception >> > >> > Me too. I guess it depends very much on whether one can afford to buy >> > a g

Re: "Ask HN: What do you want to see in Ubuntu 17.10?"

On Apr 05 2017, Ian Jackson wrote: > Florian Lohoff writes ("Re: "Ask HN: What do you want to see in Ubuntu > 17.10?""): >> On Wed, Apr 05, 2017 at 02:56:04PM +1000, Russell Stuart wrote: >> > As far as I can tell, for laptop's rebooting is a non-issue mainly >>

Re: Help requested: Packages which FTBFS randomly

On Feb 21 2017, Vincent Bernat <ber...@debian.org> wrote: > ❦ 21 février 2017 09:48 -0800, Nikolaus Rath <nikol...@rath.org> : > >>> Your chosen build environment is not common [...] >> >> This has come up a few times now. Could someone explain what is s

Re: Help requested: Packages which FTBFS randomly

> Your chosen build environment is not common [...] This has come up a few times now. Could someone explain what is so odd about his envirnoment? It does not look unusual to me. Best, -Nikolaus -- GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F Fingerprint: ED31 791B 2C5C 1613 AF38

Re: Git hosting for code that provides Debian services

On Jan 30 2017, Lars Wirzenius wrote: > I personally don't find "open core" projects to be fully free > software, even if they follow current DFSG, OSI, and FSF criteria. This strikes me as a little odd, though. So if the company that sells the "closed shell" goes bust, would that

Accepted python-llfuse 1.2+dfsg-1 (source) into unstable

Maintainer: Nikolaus Rath <nikol...@rath.org> Changed-By: Nikolaus Rath <nikol...@rath.org> Description: python-llfuse - Python bindings for the low-level FUSE API python-llfuse-dbg - Python bindings for the low-level FUSE API (debugging symbols) python-llfuse-doc - Python bindings for t

Accepted python-llfuse 1.1.1+dfsg-7 (source) into unstable

Maintainer: Nikolaus Rath <nikol...@rath.org> Changed-By: Nikolaus Rath <nikol...@rath.org> Description: python-llfuse - Python bindings for the low-level FUSE API python-llfuse-dbg - Python bindings for the low-level FUSE API (debugging symbols) python-llfuse-doc - Python bindings

Accepted python-llfuse 1.1.1+dfsg-6 (source) into unstable

Maintainer: Nikolaus Rath <nikol...@rath.org> Changed-By: Nikolaus Rath <nikol...@rath.org> Description: python-llfuse - Python bindings for the low-level FUSE API python-llfuse-dbg - Python bindings for the low-level FUSE API (debugging symbols) python-llfuse-doc - Python bindings

Accepted s3ql 2.21+dfsg-3 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 17 Jan 2017 20:35:21 -0800 Source: s3ql Binary: s3ql s3ql-dbg Architecture: source Version: 2.21+dfsg-3 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath <nikol...@rath.org> Changed-By: Nikolaus Rath

Re: Feedback on 3.0 source format problems

On Jan 10 2017, Guido Günther <a...@sigxcpu.org> wrote: > On Wed, Jan 04, 2017 at 04:38:11PM -0800, Nikolaus Rath wrote: >> On Jan 05 2017, Brian May <b...@debian.org> wrote: >> > Vincent Bernat <ber...@debian.org> writes: >> > >> >

Re: Feedback on 3.0 source format problems

On Jan 07 2017, Thibaut Paumard wrote: > Well, just to say, I'm personally quite happy with '3.0 (quilt)'. I try > to maintain all my packages in git in unapplied state, because in my > opinion this is the sensible thing to do. When I do a > git diff upstream master >

Re: Converting to dgit

On Jan 06 2017, Sean Whitton <spwhit...@spwhitton.name> wrote: > Hello Nikolaus, > > On Thu, Jan 05, 2017 at 03:59:40PM -0800, Nikolaus Rath wrote: >> On Jan 05 2017, Sean Whitton <spwhit...@spwhitton.name> wrote: >> > On Thu, Jan 05, 2017 at 1

Accepted s3ql 2.21+dfsg-2 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 06 Jan 2017 11:29:24 -0800 Source: s3ql Binary: s3ql s3ql-dbg Architecture: source Version: 2.21+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Nikolaus Rath <nikol...@rath.org> Changed-By: Nikolaus Rath

Re: unattended-upgrades by default

On Jan 06 2017, Santiago Vila wrote: > If we want to be the Universal OS, we can't assume that any time > (not chosen by the user) is ok to do an upgrade. If we want to be the Universal OS, we can't assume that users will explicitly trigger an install of security upgrades

Re: Converting to dgit

On Jan 05 2017, Sean Whitton <spwhit...@spwhitton.name> wrote: > On Thu, Jan 05, 2017 at 12:39:25PM -0800, Nikolaus Rath wrote: >> But, as far as I can tell, doing this work up-front is much easier: > > Yes, but you have to do it every single time you make changes that

Re: Converting to dgit

On Jan 05 2017, Sean Whitton <spwhit...@spwhitton.name> wrote: > Dear Nikolaus, > > On Wed, Jan 04, 2017 at 09:44:14AM -0800, Nikolaus Rath wrote: >> No, that's a misunderstanding. >> >> "The information I need" is the Debian-specific modifications t

Re: Feedback on 3.0 source format problems

On Jan 05 2017, Brian May wrote: > Vincent Bernat writes: > >> There have been a lot of complaints about it. For me, it is a pain to >> use. Its integration with gbp is poor, it produces a messy history when >> you are working on your patches and I often run

Re: Feedback on 3.0 source format problems

On Jan 04 2017, Vincent Bernat <ber...@debian.org> wrote: > ❦ 4 janvier 2017 09:47 -0800, Nikolaus Rath <nikol...@rath.org> : > >>>>>> It's surprisingly awkward, and, at least for me, it turns out that >>>>>> externalizing my rebased b

Re: Feedback on 3.0 source format problems

On Jan 04 2017, Vincent Bernat wrote: > ❦ 4 janvier 2017 04:52 GMT, Scott Kitterman  : > It's surprisingly awkward, and, at least for me, it turns out that externalizing my rebased branch as a patch series solves many of problems

Re: Converting to dgit

On Jan 04 2017, Sean Whitton wrote: >> > I also read Russ's e-mail, but I'm not yet convinced that powerful tools >> > like `git diff` and `git log` won't be able to give you the information >> > you need pretty quickly. >> >> Can you give an example? Eg if I have to

Re: Converting to dgit

On Jan 03 2017, Russ Allbery <r...@debian.org> wrote: > Nikolaus Rath <nikol...@rath.org> writes: > >> The thing that's delivered to users in 99% of the cases is the binary >> package. In the (comparatively) rare cases where the user is retrieving >> the

Re: Feedback on 3.0 source format problems

On Jan 04 2017, Paul Wise wrote: > On Mon, Jan 2, 2017 at 1:21 AM, Guillem Jover wrote: > >> I'm interested in what things people still find so off-putting to the >> point of not wanting to use the new 3.0 source formats. > > I've been reading this thread and keep being reminded

Re: Feedback on 3.0 source format problems

On Jan 03 2017, Russ Allbery wrote: > It's surprisingly awkward, and, at least for me, it turns out that > externalizing my rebased branch as a patch series solves many of these > problems surprisingly well. All the other solutions I can think of > require one or more things I

Re: "not authorised" doing various desktoppy things

On Jan 03 2017, Ian Jackson wrote: > Recently, my nm-applet can no longer control my network-manager > daemon. I get a message saying[1]: > > "org.freedesktop.NetworkManager.network-control-request failed: not > authorized" > > I think this is related to a

Re: Converting to dgit

On Jan 04 2017, Scott Kitterman wrote: >>Curating a patch series is only 5% slower than commiting directly to >>the Git repository to me. I just have to remember to gbp pq import >>before making new changes, gbp pq export when I'm done, and once in a >>great while I have to

Re: Converting to dgit

On Jan 03 2017, Russ Allbery <r...@debian.org> wrote: > Sean Whitton <spwhit...@spwhitton.name> writes: >> On Tue, Jan 03, 2017 at 10:36:22AM -0800, Nikolaus Rath wrote: > >>> I still haven't really made up my mind if I want to use git-maint-merge >>> or g

Re: Converting to dgit

On Jan 03 2017, Sean Whitton <spwhit...@spwhitton.name> wrote: > On Tue, Jan 03, 2017 at 10:36:22AM -0800, Nikolaus Rath wrote: >> I still haven't really made up my mind if I want to use git-maint-merge >> or git-dpm. Russ recently raised a valid point with the Debian >&

Re: Feedback on 3.0 source format problems

On Jan 03 2017, Sean Whitton <spwhit...@spwhitton.name> wrote: > Hello, > > On Tue, Jan 03, 2017 at 10:39:33AM -0800, Nikolaus Rath wrote: >> > >> > git log --oneline 1.2.3..debian/1.2.3-1 -- . ':!debian' >> >> Yes, but that's not as useful as wh

Re: Feedback on 3.0 source format problems

On Jan 03 2017, Nikolaus Rath <nikol...@rath.org> wrote: > On Jan 03 2017, Sean Whitton <spwhit...@spwhitton.name> wrote: >> Hello Russ, >> >> On Mon, Jan 02, 2017 at 09:29:24AM -0800, Russ Allbery wrote: >>> Furthermore, it forces a rebased, clean

Re: Feedback on 3.0 source format problems

On Jan 03 2017, Russ Allbery <r...@debian.org> wrote: > Nikolaus Rath <nikol...@rath.org> writes: > >> For example, if you get a merge conflict when rebasing, the above >> incantation will list two commits: the original debian commit and the >> merge comm

Re: Feedback on 3.0 source format problems

On Jan 03 2017, Sean Whitton wrote: > Hello Russ, > > On Mon, Jan 02, 2017 at 09:29:24AM -0800, Russ Allbery wrote: >> Furthermore, it forces a rebased, clean representation of the patches, >> which I for one hugely prefer to the mess that you get if someone was >>

  1   2   3   4   >