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 > non-me

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) there&

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. Th

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

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

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 single

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: >> https://bugs.debian.org/cgi-bin/bugreport

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 develop

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 for

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 h

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 is

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 message. Without that info

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 profiles if they result in

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 be for wrappers, do

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 1613 AF38 8B8A D113 FC

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, and maintain that patch

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 see > a bewilderin

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 with a single Etherne

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 go about advertising such th

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 --no-install-recommends. But >

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 network? Personally, I

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 > 'https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=2825

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 for it. It may not be th

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 time or person-power

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 events into something

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

On Apr 06 2017, Gunnar Wolf 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 good laptop which works wel

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 >> > because suspend is not reliable

Re: Help requested: Packages which FTBFS randomly

On Feb 21 2017, Vincent Bernat wrote: > ❦ 21 février 2017 09:48 -0800, Nikolaus Rath  : > >>> 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

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 turn the rema

Re: Feedback on 3.0 source format problems

On Jan 10 2017, Guido Günther wrote: > On Wed, Jan 04, 2017 at 04:38:11PM -0800, Nikolaus Rath wrote: >> 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 >>

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 > I want to see only debian/

Re: Converting to dgit

On Jan 06 2017, Sean Whitton wrote: > Hello Nikolaus, > > On Thu, Jan 05, 2017 at 03:59:40PM -0800, Nikolaus Rath wrote: >> On Jan 05 2017, Sean Whitton wrote: >> > On Thu, Jan 05, 2017 at 12:39:25PM -0800, Nikolaus Rath wrote: >> >> But, as far as I can te

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 either. Nor can we assum

Re: Converting to dgit

On Jan 05 2017, Sean Whitton 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 you > want to be able to push (i.e.

Re: Converting to dgit

On Jan 05 2017, Sean Whitton 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 to the >> current upstr

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 into problems with >> .debian/.git-dpm

Re: Feedback on 3.0 source format problems

On Jan 04 2017, Vincent Bernat wrote: > ❦ 4 janvier 2017 09:47 -0800, Nikolaus Rath  : > >>>>>> It's surprisingly awkward, and, at least for me, it turns out that >>>>>> externalizing my rebased branch as a patch series solves many of >>>

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 surprisingly well. All the other solutions I can t

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 Debian patched that both >> p

Re: Converting to dgit

On Jan 03 2017, Russ Allbery wrote: > Nikolaus Rath 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 source, I am not convinced that most of these u

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 of our > discussio

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 don't really want t

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 similar problem in *-power-manager,

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 do a small bit of reba

Re: Converting to dgit

On Jan 03 2017, Russ Allbery wrote: > Sean Whitton 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 git-dpm. Russ recently raised a valid point wit

Re: Converting to dgit

On Jan 03 2017, Sean Whitton 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 >> modifications over-time b

Re: Feedback on 3.0 source format problems

On Jan 03 2017, Sean Whitton 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 what git-debc

Re: Feedback on 3.0 source format problems

On Jan 03 2017, Nikolaus Rath wrote: > 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 hu

Re: Feedback on 3.0 source format problems

On Jan 03 2017, Russ Allbery wrote: > Nikolaus Rath 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 commit. git-debcherry, on the other hand, will synthesize

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 >> packaging in Git and just random

Re: Converting to dgit

On Jan 03 2017, Ian Jackson wrote: > Sean Whitton writes ("Re: Converting to dgit (was: How to get history into > dgit)"): >> On Mon, Jan 02, 2017 at 07:22:54PM -0800, Nikolaus Rath wrote: >> > I'll have to bring this up one more time. I just read

Re: Converting to dgit

On Jan 03 2017, Sean Whitton wrote: > Hello Nikolaus, > > On Mon, Jan 02, 2017 at 07:22:54PM -0800, Nikolaus Rath wrote: >> I'll have to bring this up one more time. I just read >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794244, and that >> sounds (in

Converting to dgit (was: How to get history into dgit)

On Dec 11 2016, Nikolaus Rath wrote: >>> I would like to start using dgit for one of my packages, using the >>> dgit-maint-merge workflow. >>> If I understood correctly, following the dgit-maint-merge(7) >>> instructions for the initial setup will give me a r

Re: Feedback on 3.0 source format problems

On Jan 02 2017, 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 > packaging in Git and just randomly commits things directly to the > packaging branch intermixed with merges from up

Re: Feedback on 3.0 source format problems

On Jan 01 2017, Guillem Jover wrote: > (I'm not using because > TBH it read more like a sales brochure than a more neutral page…) TBH this feels like you're sniping at Raphael here, which I think is pretty sad and inappropriate. Best, -Nikolaus --

Re: How to get history into dgit

On Dec 11 2016, Sean Whitton wrote: > 1) Ensure HEAD is dgit-compatible. This means patches are applied, > debian/source/local-options does not exist, etc. Actually, could you expand on the "etc"? What else do I need to ensure? Best, -Nikolaus -- GPG encrypted emails preferred. Key id: 0xD113

Re: How to get history into dgit

On Dec 11 2016, Sean Whitton wrote: > Hello Nikolaus, > > On Sun, Dec 11, 2016 at 12:17:50PM -0800, Nikolaus Rath wrote: >> I would like to start using dgit for one of my packages, using the >> dgit-maint-merge workflow. > > dgit-maint-merge(7) author here. Thanks f

How to get history into dgit

Hello, I would like to start using dgit for one of my packages, using the dgit-maint-merge workflow. If I understood correctly, following the dgit-maint-merge(7) instructions for the initial setup will give me a repository with only the upstream git history, but no data from previous Debian packa

Re: Building architecture:all packages

On Nov 11 2016, Christoph Biedl wrote: > b) This is a serious issue as John D. Rebuilder should be free to choose >on which architecture to build "src:foo". > > Personally, I tend to b) since > > * there is no sane way for the maintainer to tell the world which > architecture should be used

Re: Is missing SysV-init support a bug?

On Oct 18 2016, Cameron Norman wrote: > On Tue, Oct 18, 2016 at 11:23 AM, Lars Wirzenius wrote: >> On Tue, Oct 18, 2016 at 07:34:28PM +0200, Xen wrote: >>> If that is the case then they have enbedded hostility into their name simply >>> becaus eit offends normal grammar roles. >> >> I don't that'

Re: Is missing SysV-init support a bug?

On Oct 17 2016, Bart Schouten wrote: > (And I write SystemD with caps because that makes it > easier to read, people invented capitals for a reason). What would you think some people consistently spelled your name as Bart SchouteN with the same justification? And if that set of people also happe

Confused by autoremoval

Hello, 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? The email says that: It is affected by these RC bugs: 837254: python-llfuse: FTBFS: E: pybuild pybuild:276: test: plugin distutil

Re: Alternative solution

On Sep 29 2016, Jakub Wilk wrote: > Luckily, glibc has a way to disable DNS queries without LD_PRELOAD trickery: > > $ RES_OPTIONS=attempts:0 wget http://www.example.com/ Wow, I wonder many people have used this innocent environment variable name and been bitten by weird network failures.. Couldn

Re: Is missing SysV-init support a bug?

On Aug 29 2016, Russ Allbery wrote: > Nikolaus Rath writes: >> On Aug 28 2016, Bart Schouten wrote: > >>> But that's not the relevance. The idea that systemd is clearly superior >>> to sysvinit is just something you concoct up because you don't know how &

Re: Is missing SysV-init support a bug?

On Aug 28 2016, Bart Schouten wrote: > But that's not the relevance. The idea that systemd is clearly > superior to sysvinit is just something you concoct up because you > don't know how to write a service file or script and you want to let > systemd do the hard work. How is that concoted? Yes, s

Re: copyright precision

On Aug 15 2016, Simon McVittie wrote: > On Mon, 15 Aug 2016 at 18:17:52 +0200, Stefano Zacchiroli wrote: >> The problem we're having here is clearly about *tooling*. If we had a >> good toolchain to compile and audit machine-readable debian/copyright >> files without sweating, nobody would complai

Re: Keysigning via Video Conferencing

On Jun 23 2016, ja...@teacaster.net wrote: > Hello Everyone, > > Sorry to interject in this matter however it is beginning to become > repetitive. You may be contributing to this, because you clearly haven't actually read the thread. > If a Debian Developer is to sign your key, they will need to

Re: Keysigning via Video Conferencing

On Jun 23 2016, Lars Wirzenius wrote: > On Thu, Jun 23, 2016 at 12:52:35PM -0700, Nikolaus Rath wrote: >> On Jun 23 2016, Lars Wirzenius wrote: >> > On Thu, Jun 23, 2016 at 09:23:07AM -0700, Nikolaus Rath wrote: >> >> As I said in my other email, I am wonderin

Re: Keysigning via Video Conferencing

On Jun 23 2016, Lars Wirzenius wrote: > On Thu, Jun 23, 2016 at 09:23:07AM -0700, Nikolaus Rath wrote: >> As I said in my other email, I am wondering if the extra burden is worth >> the gain in security. > > Is there an extra burden? Seems to me that it'd happen natura

Re: Keysigning via Video Conferencing

On Jun 23 2016, Ben Finney wrote: > Nikolaus Rath writes: > >> But how is your policy preventing this? > > If you're looking for claims of “This policy will absolutely guarantee > the malicious behaviour is impossible”, of course that's not a > believable

Re: Keysigning via Video Conferencing

On Jun 22 2016, Gunnar Wolf wrote: > Nikolaus Rath dijo [Wed, Jun 22, 2016 at 07:58:43AM -0700]: >> > Now, I have said this too many times, but once more: As keyring-maint, >> > we are not collecting samples of people showing valid-looking ID >> > documents to oth

Re: Keysigning via Video Conferencing

On Jun 22 2016, Lars Wirzenius wrote: > On Wed, Jun 22, 2016 at 07:58:43AM -0700, Nikolaus Rath wrote: >> On Jun 21 2016, Gunnar Wolf wrote: >> > Now, I have said this too many times, but once more: As keyring-maint, >> > we are not collecting samples of peop

Re: Keysigning via Video Conferencing

On Jun 21 2016, Gunnar Wolf wrote: > Now, I have said this too many times, but once more: As keyring-maint, > we are not collecting samples of people showing valid-looking ID > documents to others. This is one of the issues why we don't have > long-queue key signing parties: Just checking the ID o

Re: Verifying dep-5

On May 28 2016, Johannes Schauer wrote: > Hi, > > Quoting Paul Wise (2016-05-28 06:45:44) >> I think it would be interesting to automatically track how each file >> in a binary package was created and which files they were derived >> from. Then we could automatically generate proper copyright file

Re: trying to use wireless not from gnome... what's the incantation?

On May 24 2016, Britton Kerin wrote: > On Mon, May 23, 2016 at 2:35 PM, Nikolaus Rath wrote: >> On May 22 2016, Britton Kerin wrote: >>> Got a new laptop after 10 years of excellent stable ancient debian, >>> and my wireless works from gnome, and only from gnome. Un

Re: trying to use wireless not from gnome... what's the incantation?

On May 22 2016, Britton Kerin wrote: > Got a new laptop after 10 years of excellent stable ancient debian, > and my wireless works from gnome, and only from gnome. Unfortunately > I find that gnome3 is not for me. I've been trying dwm. What trouble did you have? Network manager works perfectly

Re: trying to use wireless not from gnome... what's the incantation?

On May 24 2016, Adam Borowski wrote: > But it's not without problems. The one Britton met is that NM's interface > is closely married to Gnome. I am not sure what you mean by "closely married", but NM works perfectly well for me in an i3 "environment". I am not disputing that it pulls in some Gn

Re: Bug#823465: dpkg: Won't run at all on i586 Pentium MMX due to illegal instruction

On May 11 2016, Theodore Ts'o wrote: > On Mon, May 09, 2016 at 10:21:21AM -0700, Nikolaus Rath wrote: >> > Another way is to use btrfs (or zfs or perhaps LVM snapshots): whenever >> > something goes south in a way that's not trivial to recover, you can >>

Re: Bug#823465: dpkg: Won't run at all on i586 Pentium MMX due to illegal instruction

On May 08 2016, Adam Borowski wrote: > On Sun, May 08, 2016 at 02:20:45PM +0200, Marc Haber wrote: >> Tracking sid is a good idea if you can debug and fix breakages. If you >> want to be warned for disruptions, use something that we actually >> released. > > Another way is to use btrfs (or zfs or

Re: Packaging of static libraries

On Apr 19 2016, Bas Wijnen wrote: > On Thu, Apr 14, 2016 at 02:57:00PM +0200, Vincent Danjean wrote: >> > If users have such specialized needs, I think it is not only reasonable >> > that >> > they build their own versions of their libraries; I expect them to prefer >> > that. >> > So we should

Re: Bug#821035: ITP: luksipc -- LUKS in-place conversion tool

On Apr 17 2016, Philipp Kern wrote: > On Thu, Apr 14, 2016 at 10:06:51PM +0200, Vincent Bernat wrote: >> * Package name: luksipc >> Version : 0.04 >> Upstream Author : Johannes Bauer >> * URL : http://johannes-bauer.com/linux/luksipc/ >> * License : GPL-3 >> P

Re: collab-maint access for non DD on Alioth: am I using the right procedure?

On Mar 13 2016, Christian PERRIER wrote: > Quoting Cyril Brulebois (k...@debian.org): > >> Maybe such requests are processed in batch… Letting nm@ know you started >> a discussion on dd@ looks like a good idea, so I'm cc-ing them. > > That's right. SOrry for not doing that at first glance. Please

Re: Bug#815675: ITP: ftpbackup -- Script to backups your data from a Debian system to a ftp space

On Feb 24 2016, Carl Chenet wrote: > - First please Nikolau, spare me the "I don't believe Debian developers > blablabla", this try to patronize me is offending. Don't like the script > and you think it should not be in Debian or even exist? Fine, let's > discuss about it. [..] > - I'm really awar

Build depend on version range?

Hello, Is there a way to build-depend on a range of versions (e.g. newer than 0.43, but older than 1.0)? https://www.debian.org/doc/debian-policy/ch-relationships.html says: , | All of the fields except for Provides may restrict their | applicability to particular versions of each named pa

Re: Bug#815675: ITP: ftpbackup -- Script to backups your data from a Debian system to a ftp space

On Feb 23 2016, Nikolaus Rath wrote: > On Feb 23 2016, Simon McVittie wrote: >> On Tue, 23 Feb 2016 at 15:45:59 +0100, Carl Chenet wrote: >>> Description : Script to backup your data from a Debian system to a >>> ftp space >> >> Backups via ftp? In

Re: Bug#815675: ITP: ftpbackup -- Script to backups your data from a Debian system to a ftp space

On Feb 23 2016, Simon McVittie wrote: > On Tue, 23 Feb 2016 at 15:45:59 +0100, Carl Chenet wrote: >> Description : Script to backup your data from a Debian system to a ftp >> space > > Backups via ftp? In 2016? > > I don't think Debian should be encouraging backups that don't have [...] Al

Re: [Mailman-Developers] Let's try to package mailman3 in Debian!

On Feb 22 2016, Malte Swart wrote: >> > - The documentation's raw rst files are currently installed; please run >> > sphinx> >> > during the build and ship the compiled files instead. >> >> Lintian complains about external js library that is used in html doc. >> (jquery as far as I remember) I

Re: Going ahead with non-free-firmware

On Jan 09 2016, Dominic Hargreaves wrote: > I think the *policy* for this section should be firmware, as defined > as code not executing on the main CPU, or something like that. Uh, so intel-microcode is still out? Description: Processor microcode firmware for Intel CPUs This package contains

Re: support for merged /usr in Debian

On Jan 10 2016, Eric Valette wrote: > Russ Allbery writes: > >> For one specific example, it's become quite clear over the past year that >> systemd has achieved the same status as abortion debates in US politics. >> Not only is it clear that we will *never* stop arguing about systemd, >> oppositi

Re: support for merged /usr in Debian

On Jan 08 2016, Tobias Frost wrote: > Am Freitag, den 08.01.2016, 09:14 -0800 schrieb Nikolaus Rath: >>  Debian is developed by its developers, not by its users. Do you have >> any evidence (other than your opinion) that loss of users would cause >> loss of development work?

Re: support for merged /usr in Debian

On Jan 08 2016, Svante Signell wrote: > On Thu, 2016-01-07 at 22:46 +0100, Philip Hands wrote: >> Marc Haber writes: >> >> > On Tue, 5 Jan 2016 19:37:03 +0100, Marco d'Itri wrote: >> > > On Jan 05, Ian Jackson wrote: >> > > >> > > > People who have been using a configuration for many years na

Re: support for merged /usr in Debian

On Jan 06 2016, Ian Jackson wrote: > Nikolaus Rath writes ("Re: support for merged /usr in Debian"): >> On Jan 05 2016, Ian Jackson wrote: >> > People who have been using a configuration for many years naturally >> > become upset when they are told that it h

Re: support for merged /usr in Debian

On Jan 05 2016, Ian Jackson wrote: > Marco d'Itri writes ("Re: support for merged /usr in Debian"): >> On Jan 05, Ian Jackson wrote: >> > or which do mount /usr using / rather than initramfs, or some such. >> >> And this has already not been supported for many years, even if it works >> in some

Re: support for merged /usr in Debian

On Jan 05 2016, Marc Haber wrote: > On Mon, 4 Jan 2016 22:21:06 +0100, Iustin Pop > wrote: >>On 2016-01-04 12:03:07, Marc Haber wrote: >>> On Sun, 3 Jan 2016 19:15:18 +0100, m...@linux.it (Marco d'Itri) wrote: >>> >Anyway, if you think that the merged /usr scheme is about systemd then >>> >you a

Re: How shall I report a bug in the .deb packaging itself?

On Dec 24 2015, David Kalnischkies wrote: > Asking the user to confirm each and every removal would end up being > pretty annoying very fast and if its something you don't want to train > users to do, its is brainlessly pressing yes a hundred times as the > important question nr 101 will surely be

  1   2   3   >