Re: About license compatibility

Le 05/12/2019 à 16:57, Boyuan Yang a écrit : >> There are many packages having a different license in the Debian >> distribution. >> How to resolve a conflict between licenses to specify GPLv2? >> For instance, GPLv2 & GPLv3 are incompatible. > > I never heard that GPLv2 license and GPLv3 license

Re: Do we want to Require or Recommend DH

Le 14/05/2019 à 11:07, Andreas Tille a écrit : > Can you give an example for a package that has a non-dh rules file > "working for years" that gives as a result a package with no lintian > warnings without changing this d/rules file? Turns out I can't... I was thinking of some packages that I didn

Re: Do we want to Require or Recommend DH

Hi, Le 13/05/2019 à 14:33, Sam Hartman a écrit : > Why Would we Want This? > === dh is gret for the vast majority of packages. Whenever your rules files ends up with the simple catch all line, plus a couple of auto_something overrides, its probably the best solution. For com

Bug#918796: ITP: yorick-full -- full installation of the Yorick interpreter and add-ons

Package: wnpp Severity: wishlist Owner: Thibaut Paumard * Package name: yorick-full Version : 2.2.04+dfsg1+full Upstream Author : Thibaut Paumard * URL : http://yorick.sourceforge.net * License : GPL-2+ Programming Lang: None (metapackage) Description

Re: Updating the Maintainer field in preparation for Alioth's shutdown?

Le 16/02/2018 à 14:10, Raphael Hertzog a écrit : Yes, you can put team+@tracker.debian.org in your Maintainers fields. eg. team+pkg-secur...@tracker.debian.org for https://tracker.debian.org/teams/pkg-security/ It's possible to use this right now (it will not generate any bounce) but direct ma

Re: Debian part of a version number when epoch is bumped

Le 15/02/2018 à 14:15, Vincent Bernat a écrit : ❦ 15 février 2018 13:36 +0100, Thibaut Paumard  : I meant not implemented for java, specifically. But I was wrong: we do have e.g. java8-runtime-headless listed in https://www.debian.org/doc/packaging-manuals/virtual-package-names-list.txt So

Re: Debian part of a version number when epoch is bumped

Le 15/02/2018 à 13:03, gregor herrmann a écrit : On Thu, 15 Feb 2018 10:58:01 +0100, Thibaut Paumard wrote: The "Provides: foo-api (>= 1.8)" mentioned elsewhere in the thread sounds also neat for java packages, but it does not seem to be implemented. It's '(= $version

Re: Debian part of a version number when epoch is bumped

(Please follow-up to debian-curiosa) Le 15/02/2018 à 11:41, Simon McVittie a écrit : We don't have to look far to find a weird versioning scheme that can't be represented without epochs: our largest competitor in the field of general-purpose operating systems has such a versioning scheme. Imagi

Re: Debian part of a version number when epoch is bumped

Le 14/02/2018 à 18:52, Vincent Bernat a écrit : More concrete example (now a bit in the past). On Wheezy, you want to depend on a 1.8 JRE (you package independently). You put default-jre-headless (>= 1.8). Since you have forgotten about the epoch, this pulls Wheezy default-jre-headless (1:1.7-47+

Re: salsa.debian.org (git.debian.org replacement) going into beta

Le 26/12/2017 à 21:34, Ole Streicher a écrit : I agree with your reasoning. I just wanted to highlight that the situation is in fact worse with the "Team foo " schema: Our tools do not seem ready for that yet. I fully agree here. It makes pages like https://qa.debian.org/developer.php?email=d

Re: ISO download difficult

Dear Jonas, Le 05/12/2017 à 10:39, Jonas Meurer a écrit : On Mon, Dec 04 2017, Thibaut Paumard wrote: I vote for:     1- putting the non-free firmware on all our images, This seems more controversial than it needs to be, and misses an opportunity for us to express our values. [...] I also

Re: ISO download difficult

Dear Sean, Le 04/12/2017 à 21:47, Sean Whitton a écrit : Hello, On Mon, Dec 04 2017, Thibaut Paumard wrote: I vote for: 1- putting the non-free firmware on all our images, This seems more controversial than it needs to be, and misses an opportunity for us to express our values. Why

Re: ISO download difficult

Hi, Le 01/12/2017 à 22:14, Luca Capello a écrit : Like the following? Which is 3-click away from the main page: Three clicks away is three clicks too much. We have a nice "download" button on the front page, suggesting that you

Re: Bug#858612: ITP: wifiphisher -- Automated phishing attacks against Wi-Fi networks

Hi, Le 25/03/2017 à 11:44, Raphael Hertzog a écrit : > Hi, > > On Sat, 25 Mar 2017, Thibaut Paumard wrote: >> I'm not sure of the benefit for the project of shipping this, > > This is a tool that is shipped in Kali Linux, a Debian derivative and we > are trying

Re: Bug#858612: ITP: wifiphisher -- Automated phishing attacks against Wi-Fi networks

"Interesting" software.I'm not sure of the benefit for the project of shipping this, but do we have ways of protecting our users from it?Regards, Thibaut.Le 24 mars 2017 2:19 PM, Sophie Brun a écrit :Package: wnpp Severity: wishlist Owner: Sophie Brun * Package name    : wifiphisher   Versi

Re: Depends/Recommends from libraries

Dear Ian, Le 09/03/2017 à 18:39, Ian Jackson a écrit : > Thibaut Paumard writes ("Re: Depends/Recommends from libraries"): >> There are quite legitimate uses for dependencies or recommendations in >> libraries. For instance, tne library that I maintain (libgyoto) has the

Re: Depends/Recommends from libraries

Le 08/03/2017 à 23:33, Adam Borowski a écrit : > Hi, mortals and paultag! > > 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)

Re: De-Branding of Icedove, reintroducing Thunderbird packages into Debian

Le 19/02/2017 à 08:37, Carsten Schoenert a écrit : > Hello, > > Am 19.02.2017 um 07:12 schrieb Josh Triplett: >> Mike Hommey wrote: >>> Why not just create a ~/.thunderbird symlink to ~/.icedove if >>> ~/.icedove exists? >> >> This seems like the right solution. (Or, equivalently, rename >> ~/.ic

Re: De-Branding of Icedove, reintroducing Thunderbird packages into Debian

Le 16/02/2017 à 20:00, Carsten Schoenert a écrit : > Am 16.02.2017 um 19:26 schrieb Michael Biebl: >> You already have a NEWS entry for the de-branding which talks about the >> user profile. Maybe add an additional section there, that the old >> profile is kept as ~/.icedove and that the user can d

Re: Help requested: Packages which FTBFS randomly

Dear Santiago, Le 15/02/2017 à 18:26, Santiago Vila a écrit : > Hello. > > The following packages FTBFS for me randomly. First column is the bug > number, second column is the estimated probability of failure in my > build environment, which is described here: > > https://people.debian.org/~sanv

Re: Where to report Wayland-related bugs

Le 03/02/2017 à 14:33, Michael Biebl a écrit : > Hi there > > Am 03.02.2017 um 13:00 schrieb Thibaut Paumard: >> Le 03/02/2017 à 12:35, Emilio Pozuelo Monfort a écrit : >>> On 03/02/17 11:42, Thibaut Paumard wrote: >>>> I am seeing issues in some softw

Re: Where to report Wayland-related bugs

Le 03/02/2017 à 12:35, Emilio Pozuelo Monfort a écrit : > On 03/02/17 11:42, Thibaut Paumard wrote: >> I am seeing issues in some software that don't seem usable at all in >> GNOME Wayland, e.g.: >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852699 >>

Where to report Wayland-related bugs

Dear fellow developers, I have started using GNOME Wayland possibly as my primary session. It sort of feels different from the default X11 GNOME session in surprising ways (overall rather more comfortable I would say). I am seeing issues in some software that don't seem usable at all in GNOME Way

Re: Feedback on 3.0 source format problems

Le 07/01/2017 à 22:10, Nikolaus Rath a écrit : > 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 t

Re: Feedback on 3.0 source format problems

anage it. I manage my patches using quilt. I would really prefer if sbuild et al. would revert the patches after building by default, but that's life. I respect that other people have other views. I'm not interested at the moment in dgit or other wrappers because 1- they seem to me to add com

Re: about build flavours

Dear Sascha, Le 29/11/2016 à 15:24, Sascha Steinbiss a écrit : >>> >>> Then, we conflict the packages with each other and dpkg-divert the >>> /usr/bin/suricata file in suricata-hyperscan. >> >> If both packages conflict with each other, then you don't need >> dpkg-divert. > > One could think of

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

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Le 08/11/2016 à 15:13, Alec Leamas a écrit : > > Trying to understand the debhelper, dh-exec and dh-exec-subst > manpages. However, I just don't get it. All these tools seems to > be about changing the actual location of certain files by > substi

Re: Multi-Arch: allowed

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Dear David, Le 02/11/2016 à 01:05, David Kalnischkies a écrit : > I would add: > > * Check if gyoto-bin really needs to be M-A:allowed. Name, > Description and the list of filenames included in the package > suggest to me that the package can and

Re: Multi-Arch: allowed

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Dear David, Le 01/11/2016 à 15:57, David Kalnischkies a écrit : > On Tue, Nov 01, 2016 at 02:43:21PM +0100, Thibaut Paumard wrote: >> How do you actually use Multi-Arch: allowed? Should a dependent >> package then specify either :s

Multi-Arch: allowed

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Dear all, How do you actually use Multi-Arch: allowed? Should a dependent package then specify either :same or :foreign? Looks like it's not working: https://piuparts.debian.org/sid/fail/gyoto-dbg_1.1.1-1.log I was able to find documentation about

Re: Bug#835533: dasher: Please package Dasher 5.0 beta

month. > > I'm sorry for not stating that in dasher's bugs, but I would have > shared my plans > if I knew about the removal. > > Thibaut Paumard already filed an ITP and thank you for that. Dear Bálint, I'm working on reintroducing dasher with minimal chang

Bug#839836: ITP: dasher -- A graphical predictive text input system

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Package: wnpp Severity: wishlist Owner: Thibaut Paumard * Package name: dasher Version : 5.0 Upstream Author : The Dasher Project * URL : http://www.inference.phy.cam.ac.uk/dasher/ * License : GPL Programming

Re: Reupload package already in the NEW queue

Le 20/09/2016 à 14:43, Rene Engelhard a écrit : > [ this is more for -mentors I think.. ] > > On Tue, Sep 20, 2016 at 02:24:24PM +0200, Thibaut Paumard wrote: >> 1- simply compile and upload normally > > .. with a new version .. Thanks Rene, uploaded. > >> 2- s

Reupload package already in the NEW queue

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi there, I feel this question must be fairly simple, but I couldn't find the answer anywhere I looked. I have a package in NEW (lorene, to be precise). It's an entirely new package. Since it is in the queue, I have been able to improve it. The im

Bug#837556: ITP: lorene -- framework for numerical relativity

Package: wnpp Severity: wishlist Owner: Thibaut Paumard * Package name: lorene Version : 0.0.0~cvs20160908+dfsg Upstream Author : Eric Gourgoulhon, Philippe Grandclément, Jérôme Novak et al. * URL : http://www.lorene.obspm.fr/ * License : GPL2+ Programming

Re: Key collisions in the wild

Thanks Samuel, Looks like my key has been purposefully collided too, already two years ago: thibaut$ LANG=C gpg --search-key thib...@debian.org gpg: searching for "thib...@debian.org" from hkp server pgp.mit.edu [snip] (2) Thibaut Paumard 4096 bit RSA key E0DC2840, cre

Re: Key collisions in the wild

Le 10/08/2016 01:23, Thibaut Paumard a écrit : > Thanks Samuel, > > Looks like my key has been purposefully collided too, already two years ago: > > thibaut$ LANG=C gpg --search-key thib...@debian.org > gpg: searching for "thib...@debian.org" from hkp server pgp.mit.

Re: Copyright format “License” field: grant of license, license text?

> How about this:: > > Files: * > Copyright: 2012-2014, Toby Inkster > License: Artistic or GPL-1+ > License-Grant: > This is free software; you can redistribute it and/or modify it under > the same terms as the Perl 5 programming language system itself. > Com

Re: Blends and (astronomy) meta-packages

Hi Ole, (Please do choose a followup-to as Jonas suggested) Le 10/05/2015 13:03, Ole Streicher a écrit : > 1. Create a meta-package within python-astropy: This would concentrate the > management in this package which is maybe not the best idea (development > of affiliated packages is independent

Re: Bits from the dpkg project: 1.17.x series, general news

Hi, Le 18/04/2015 21:27, Guillem Jover a écrit : > Portability in dpkg is very important, to be able to support downstreams > and people who use it on other systems, or even package it in other > (non-GNU/Linux) distributions. But for many such systems I'm currently > porting purely throu

Re: network-manager-strongswan kicked out from Jessie, even though there is a fix?

Le 05/02/2015 16:09, Harald Dunkel a écrit : > On 02/05/15 15:38, Dominique Dumont wrote: >> >> Sorry that's not possible: this package was removed from Jessie back in >> September. Freeze policy excludes package removed more than 1 week ago [1] >> > > Highly discouraging. Feels like I wasted my

Re: RFC: DEP-14: Recommended layout for Git packaging repositories

Le 12/11/2014 12:25, Raphael Hertzog a écrit : > Hi, > > On Wed, 12 Nov 2014, Thibaut Paumard wrote: >> I see nothing about whether the debian branch should contained the >> unpacked or the unpacked *and* patched sources, and whether to ship the >> .pc directory. >

Re: RFC: DEP-14: Recommended layout for Git packaging repositories

Le 11/11/2014 22:26, Raphael Hertzog a écrit : > Hello, > > following the initial discussion we had in August > (https://lists.debian.org/debian-devel/2014/08/thrd2.html#00499), I have > written a first draft of the Debian Enhancement Proposal that I suggested. > It's now online at http://dep.debi

Re: Hurra for an efficient ftpmaster team!

Le 22/10/2014 19:04, Jonas Smedegaard a écrit : > Hurra for the ftmaster team! +1 \o/ and a standing ovation signature.asc Description: OpenPGP digital signature

Re: The inittab interface - Re: Bug#766187: runit: Fails to install runit after fresh install of jessie beta2

Le 22/10/2014 11:20, Gerrit Pape a écrit : > severity 766187 grave > quit > > [...] > When switching to sysvinit, the /etc/inittab file is created, but > doesn't include the lines enabling the runit supervision. After reboot > runit supervision will not be enabled, although the package is > insta

Re: Bug#763450: ITP: python-sysv-ipc -- semaphores, shared memory and message queues

Le 30/09/2014 13:31, Thomas Goirand a écrit : > Package: wnpp > Severity: wishlist > Owner: Thomas Goirand > > * Package name: python-sysv-ipc > Version : 0.6.8 > Upstream Author : Philip Semanchuk > * URL : http://semanchuk.com/philip/sysv_ipc/ > * License :

Re: Trimming priority:standard

Le 12/09/2014 16:37, Thorsten Glaser a écrit : > On Fri, 12 Sep 2014, Thibaut Paumard wrote: > >> No, it's not. The actual definition is very vague and does not refer to > > Oh, my bad. I confused this with priority:important then. > > So we should probably *raise

Re: Trimming priority:standard

Le 12/09/2014 16:33, Thibaut Paumard a écrit : > Le 12/09/2014 16:23, Thorsten Glaser a écrit : >> On Fri, 12 Sep 2014, Thibaut Paumard wrote: >> >>> I agree that all those tools belong to a standard UNIX system. However, >>> is that among our goals to provide peop

Re: Trimming priority:standard

Le 12/09/2014 16:23, Thorsten Glaser a écrit : > On Fri, 12 Sep 2014, Thibaut Paumard wrote: > >> I agree that all those tools belong to a standard UNIX system. However, >> is that among our goals to provide people with a standard UNIX system by > > This is not about

Re: Trimming priority:standard

Le 12/09/2014 15:49, Thorsten Glaser a écrit : > On Fri, 12 Sep 2014, Josh Triplett wrote: [...] > bc is the standard Unix calculator, normally a dc frontend, > and used in *a lot* of scripts. [...] > Eh sorry? at+cron are standard Unix. [...] > But then, an MTA configured to listen and deliver loc

Re: rename source package

ote that the deb ball associated to it is already named gap-guava. > Hi Jerôme, (This is rather a question for -mentors, hence the reply-to). There are several solutions, see https://wiki.debian.org/Renaming_a_Package. Kind regards, Thibaut. -- * Dr Thibaut Paumard | LESIA/CNRS - T

Re: How to build-depend on a C++11-capable compiler?

ilities in these? Anyway, I think I'll just go ahead and don't build-depend on a specific compiler, because Gyoto can be built already with Wheezy's default compiler in C++11 mode. Thanks all for your tips. Kind regards, Thibaut. -- * Dr Thibaut Paumard | LESIA/CNRS - Tab

How to build-depend on a C++11-capable compiler?

Hi, The new release of my package Gyoto should be built preferably with a C++11-capable compiler. It can be built with a reduced feature-set without, though. Is there a clever way to ensure that the default compiler is C++11-capable, if available in the archive, or should I simply Build-Depend on

Re: Alioth tracker

Le 25/06/2014 08:49, Raphael Hertzog a écrit : > This happened a few times already but only with well know DD. For what it's worth, Ole is well known an respected in the area in which he has contributed most, the Debian Astro team, which he created. Kind regards, Thibaut. signature.asc Descri

Re: Demande

[Redirecting this mail of a prospective French contributor] Le 21/05/2014 12:58, nadia ziane a écrit : > Je suis ingénieur en informatique , et j'aimerais bien rejoindre > l'équipe de développement debian mais j'aimerais savoir quels sont les > conditions pour y faire? quels sont les connaissanc

Re: systemd-fsck?

Le 15/05/2014 10:55, Gergely Nagy a écrit : > You do realise we have one libc (sure, you can install *additional* > ones, but we have one libc the archive is compiled against), we have one > package manager (you can, of course, install rpm too, it is packaged!), > we have one "make" we use to build

Re: systemd-fsck?

Le 13/05/2014 19:38, Thorsten Glaser a écrit : > Cyril Brulebois dixit: > >> The sad thing is: almost nobody reads the release notes. > > Many people run testing or unstable, so there are no “release”s > to have notes for, either… (but yes, even those who run stable > don’t). People who run test

Re: systemd-fsck?

Hi, Le 13/05/2014 17:36, Russ Allbery a écrit : > Right, which I've been arguing for already in this thread. I don't think > we should force this on upgrades. There should be a prompt and an > opportunity to not change init systems. Instead of or in addition to such prompting, I expect this swi

Re: systemd patent fees - who pays?

Le 28/03/2014 11:40, Sebastian Feld a écrit : > Now that Redhat and Suse have been contacted by ORACLE regarding to > licensing the SMF patents a question arises for Debian: Patent infringement claims by big companies are often FUD. The right channel if you really want to discuss this (rather tha

Re: Bug#740946: ITP: libsub-recursive-perl -- anonymous memory leak free recursive subroutines

Le 06/03/2014 15:32, Peter Roberts a écrit : > Description : anonymous memory leak free recursive subroutines Hi, I suggest using hyphens and comas in the short title: "anonymous, memory-leak-free, recursive subroutines". Initially I thought you were packaging a free package for leaking mem

Re: Bits from keyring-maint: Pushing keyring updates. Let us bury your old 1024D key!

Le 05/03/2014 10:01, Didier 'OdyX' Raboud a écrit : > Le mercredi, 5 mars 2014, 10.47:07 Paul Wise a écrit : >> On Wed, Mar 5, 2014 at 1:55 AM, Xavier Roche wrote: >>> I have a rather silly question: would a mail (signed with this key) >>> request to the DDs who already signed the initial key (and

Bug#740728: ITP: yorick-ynfft -- nonequispaced fast Fourier transform for Yorick

Package: wnpp Severity: wishlist Owner: Thibaut Paumard * Package name: yorick-ynfft Version : 0.0.1 Upstream Author : Éric Thiébaut * URL : http://cral.univ- lyon1.fr/labo/perso/eric.thiebaut/?Software/Yorick/YNFFT * License : CeCILL-C Programming Lang: C

Re: contrib and nonfree distribs

Le 28/02/2014 12:56, Solal Rastier a écrit : > Further proof that Debian is proprietary software... I applause this almost inconspicuous troll attempt. Please don't top-post. http://www.caliburn.nl/topposting.html Regards. PS: full stop. > > Le 28 févr. 2014 à 12:46, Wouter Verhelst a écrit :

Re: when will we finally throw away binary uploads (Re: Please upgrade your build environment when you are affected by transition

Hi, Le 26/02/2014 15:55, Jakub Wilk a écrit : > * Paul Tagliamonte , 2014-02-26, 08:39: >>> First, we need new syntax to specify the architectures an arch:all >>> package may be built on. (There may be cases where this cannot be >>> deducted from the other binary packages it builds – if any. Heck,

Re: C++ testing library

Le 20/02/2014 18:12, Jan Gloser a écrit : > Hello people, > > Earlier this week I wanted to find a C++ testing library. I tried gtest > and cppunit but both of them seemed way too much overkill for my needs. > So I wrote this: > > https://github.com/renra/prehash_challenge_phasor_cpp/blob/master/

Re: let's split the systemd binary package

Le 24/10/2013 17:08, Uoti Urpala a écrit : > Surely you won't claim that tools > depending on systemd as init is an argument to not use systemd as init! It's an argument for not depending on those tools, since we don't want to (and can't) rely on systemd being the init system. Regards. signat

Re: let's split the systemd binary package [Was, Re: systemd effectively mandatory now due to GNOME]

Le 24/10/2013 10:54, Jonathan Dowland a écrit : > On Wed, Oct 23, 2013 at 06:27:51PM -0700, Steve Langasek wrote: >> So first of all, how hard it is to split is irrelevant. This is work >> that must be done, and Debian should not accept excuses for it not >> being done. > > I have a lot of respec

Re: Archive rebuild failures and the clean target

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Le 07/10/2013 11:31, Sven Joachim a ￩crit : > On 2013-10-07 10:53 +0200, Thibaut Paumard wrote: > >> I think people who do full archive rebuilds should fix their >> scripts to not clean before building, or file "wishl

Archive rebuild failures and the clean target

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, I see "serious" FTBFS bugs appearing on my packages when people try to rebuild the entire archive. Those failures are due to attempting to run the clean target prior to anything else. While it's nice when debian/rules clean works even on alrea

Re: best policies for third party Debian packaging and get-orig-source target

Le 29/07/2013 12:54, Faheem Mitha a écrit : > > Hi, > > I've got Debian packaging for a piece of software I've written. This > software probably is too specialized to be part of Debian. In any case, > for now I have no plans to try to include it in Debian. However, I'd > like to follow best pract

Re: default MTA

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Le 29/05/2013 21:52, Marc Haber a écrit : > But, alas, people are going to report every single mail in the > local mailbox als Spam to their ISP. > MUAs tend to present mail in "folders" by "accounts". They can be configured to display local mail i

Re: default MTA

Le 28/05/2013 21:12, Tzafrir Cohen a écrit : > On Tue, May 28, 2013 at 07:10:51PM +0200, Matthias Klumpp wrote: > Forwarding root's mail to all users in the group users. Then using the > standard mail clients (kmail, evolution or even mutt). > Hi, 1- Not every user should be permitted to read ro

Re: default MTA

Le 28/05/2013 21:51, Adam Borowski a écrit : > On Tue, May 28, 2013 at 05:58:15PM +0200, Thibaut Paumard wrote: >> We could imagine running a simple biff applet by default in every >> desktop interface, and clicking it could trigger a simple mail reader, >> configured for

Re: default MTA

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, Le 28/05/2013 17:21, Adam Borowski a écrit : >> >> We are talking about a default configuration, and the only useful >> thing in a default configuration is local mail. Local mail not >> being read by anyone on most machines. > > If you don't r

Re: Is there an active Debian mactel team?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Le 23/05/2013 09:42, Thibaut Paumard a écrit : > > Dear all, > > Despite all the efforts from many people, it's still quite > difficult to get a fully functional Debian system on certain Apple > hardware. > > I h

Re: Is there an active Debian mactel team?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Le 24/05/2013 11:50, Vincent Cheng a écrit : > On Thu, May 23, 2013 at 12:42 AM, Thibaut Paumard > wrote: >> >> Dear all, >> >> Despite all the efforts from many people, it's still quite >> difficult t

Is there an active Debian mactel team?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Dear all, Despite all the efforts from many people, it's still quite difficult to get a fully functional Debian system on certain Apple hardware. I have been looking for a team I could join to discuss and improve the situation, but I could not fin

Bug#709284: ITP: yorick-gy -- GObject introspection bindings for the Yorick language

Package: wnpp Severity: wishlist Owner: Thibaut Paumard Hi, * Package name: yorick-gy Version : 0.0.1 Upstream Author : Thibaut Paumard * URL : https://github.com/paumard/yorick-gy * License : GPL Programming Lang: C, Yorick Description : GObject

Re: Bug#706605: ITP: macfanctld -- Fan control daemon for Apple MacBook computers

Dear Paul, On 02/05/2013 13:04, Paul Wise wrote: On Thu, May 2, 2013 at 5:34 PM, Thibaut Paumard wrote: Description : Fan control daemon for Apple MacBook computers Sounds similar to thinkfan for Thinkpads, some questions: [...] can we get a generic daemon that works for all laptops

Re: Bug#706605: ITP: macfanctld -- Fan control daemon for Apple MacBook computers

Hi, I include below an answer from upstream, who only replied to the bug report: On 02/05/2013 13:04, Paul Wise wrote: On Thu, May 2, 2013 at 5:34 PM, Thibaut Paumard wrote: Description : Fan control daemon for Apple MacBook computers Sounds similar to thinkfan for Thinkpads, some

Bug#706605: ITP: macfanctld -- Fan control daemon for Apple MacBook computers

Package: wnpp Severity: wishlist Owner: Thibaut Paumard * Package name: macfanctld Version : 0.6 Upstream Author : Mikael Strom * URL : https://github.com/MikaelStrom/macfanctld * License : GPL Programming Lang: C Description : Fan control daemon for

Re: Go (golang) packaging, part 2

Le 30/01/2013 09:55, Paul Wise a écrit : > On Wed, Jan 30, 2013 at 11:15 AM, Chow Loong Jin wrote: > >> Having multiple package managers which don't know about each other on a >> system >> is evil™ (but in some cases, can be managed properly). > > Some integration between dpkg and domain-specifi

Re: pidstat

Le 28/01/2013 10:47, vangelis mouhtsis a écrit : > Dear Developers, > How this package, named _pidstat _works on Debian? or i'm looking for > ghosts? > > http://linuxaria.com/howto/linux-terminal-pidstat-know-everything-about-your-processes?lang=en > > Thanks in advance > gnugr > -- Hi, this i

Re: Getting rid of an obsolete library package or let's say byebye to libsox-fmt-ffmpeg

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Le 21/01/2013 16:06, Pascal Giard a écrit : > In what seems to be in retrospect a misstep, I've uploaded a > version of sox (14.4.0-5) to fix #676167 [3] but that also has > disabled ffmpeg. I moved ahead as looking at the reverse > dependencies, I

Re: Fwd: procenv_0.9-1_source.changes REJECTED

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Le 20/11/2012 14:35, Dmitrijs Ledkovs a écrit : > What's this: lucatelli Kernel: Linux 3.2.0-0.bpo.3-octeon > https://buildd.debian.org/status/fetch.php?pkg=llvm-3.2&ver=3.2~rc1-1~exp3&arch=mips&stamp=1353416035 > > Why is distribution (experiment

Re: Fwd: procenv_0.9-1_source.changes REJECTED

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Le 20/11/2012 13:37, Dmitrijs Ledkovs a écrit : > On 20 November 2012 11:45, Jon Dowland wrote: >> On Tue, Nov 20, 2012 at 11:10:37AM +, Dmitrijs Ledkovs >> wrote: >>> I currently do not have facilities to build the package in >>> question with

Re: Bugs filed in unexpected places

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Le 26/10/2012 15:24, Andrei POPESCU a écrit : > Hi all, > > The discussion about ITO made me think: wouldn't it make more sense > to also have RFH, RFA, and O filled against the package itself and > not wnpp? One has to be quite familiar with Debian

Re: [SUMMARY/PROPOSAL] Orphaning another maintainer's packages - maintainer's objection

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Le 26/10/2012 08:46, Bart Martens a écrit : > On Thu, Oct 25, 2012 at 12:45:21PM -0400, Scott Kitterman wrote: >> Gergely Nagy wrote: AIUI, with the current >> proposal, as long as three DDs think it should be orphaned, the >> maintainer's objection

Re: [SUMMARY/PROPOSAL] Orphaning another maintainer's packages - skipping pointless delay

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Le 26/10/2012 08:35, vangelis mouhtsis a écrit : > Hi, I'm wondering, before a package will be orphaned is it > possible/ needful the owner to ask for help or to express the > reasons? > > Regards gnugr http://www.debian.org/devel/wnpp/ Look for "R

Re: Discarding uploaded binary packages

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Le 26/10/2012 02:13, Peter Miller a écrit : > It may be possible to address both concerns in a different way. > > 1. Implement PPAs. The code is open source, get it working first, > and enhance it later. > > 2. DDs and DMs upload source-only to th

Re: [SUMMARY/PROPOSAL] Orphaning another maintainer's packages

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Le 25/10/2012 15:50, Ian Jackson a écrit : > I'm also not that keen on the idea that the outcome is to orphan > the package. The salvager should surely be adding themselves as > an Uploader. Is that in addition to or instead of orphaning the packag

Re: [SUMMARY/PROPOSAL] Orphaning another maintainer's packages

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Le 25/10/2012 01:51, Steve Langasek a écrit : > On Thu, Oct 25, 2012 at 08:38:19AM +0900, Charles Plessy wrote: >> Le Wed, Oct 24, 2012 at 09:46:08PM +, Clint Adams a écrit : >>> On Wed, Oct 24, 2012 at 11:48:12AM -0700, Steve Langasek >>> wrote:

Re: (seemingly) declinging bug report numbers

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Le 11/10/2012 17:29, Tollef Fog Heen a écrit : > ]] Thibaut Paumard > >> Users who get software through the Debian packages are still >> 100% users of said software. > > This might be your impression. It does not at a

Re: (seemingly) declinging bug report numbers

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Le 11/10/2012 13:40, Stefano Zacchiroli a écrit : > On Thu, Oct 11, 2012 at 11:51:50AM +0200, Christoph Anton Mitterer > wrote: >> On Thu, 2012-10-11 at 09:15 +0200, Mathieu Malaterre wrote: >>> I believe the script is incorrect. It does not count ub

Re: Question about debian experimental.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 (This thread is better suited for debian-mentors, setting mail-followup-to accordingly) Le 08/10/2012 18:30, Andrej N. Gritsenko a écrit : > Hello! > > I have a question. Since maintainers of LXDE are extremely busy > last few months I would like t

Re: symlink vs. directory "conflicts"

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, Le 03/10/2012 23:24, Andreas Beckmann a écrit : > > So what is the general recommendation about packages that ship > files over symlinked directories? Should this be forbidden because > it opens cans of worms? I don't think that this should be

Re: Communication of technical committee decisions (Re: [CTTE #614907] Resolution of node/nodejs conflict)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Le 21/07/12 22:35, Filipus Klutiero a écrit : > Hi Arno, > > Arno Töll wrote: >> Hi, >> >> On 18.07.2012 02:07, Filipus Klutiero wrote: >>> Thank you, but I would appreciate if debian-devel-announce >>> would stay dedicated to important announcemen

Re: Work-needing packages report for Jul 13, 2012

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Le 13/07/12 12:41, Alberto Luaces a écrit : > Thibaut Paumard writes: > >> Le 13/07/12 11:21, Juhana Sadeharju a écrit : >>> However, I checked that openscenegraph (OSG). Seems like it is >>> not used much, but as scene

Re: Fixing the mime horror ini Debian

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Le 13/07/12 12:13, Josselin Mouette a écrit : > see is obsolete. Maybe the target for the next release could be to > get rid of it. Please don't. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) Comment: Using GnuPG with Mozilla - http:/

Re: Work-needing packages report for Jul 13, 2012

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Le 13/07/12 11:21, Juhana Sadeharju a écrit : > Is there a list of software which should be used instead of some > old software? That is, should orphaned packages stay orphaned for a > good reason. > > Also, are people wasting time in packaging oldies

  1   2   >