Re: Summary: Git Packaging Round 2 [comments by 11/05/2019]

2019-10-08 Thread Raphael Hertzog
On Tue, 08 Oct 2019, Holger Levsen wrote: > On Mon, Oct 07, 2019 at 09:22:46PM -0400, Sam Hartman wrote: > > [...] as a last opportunity for > > others to comment. > > what's the deadline to grok this 20k and respond? It's in the subject: [comments by 11/05/2019] November 5th. Cheers, --

Re: Git Packaging: Native source formats

2019-08-29 Thread Raphael Hertzog
Hi, On Wed, 28 Aug 2019, Sam Hartman wrote: > Internet is faster and disks are cheaper. I'm not sure that DSA (which is maintaining snapshot.debian.org) will be happy with this assertion. > Using native source formats (1.0 and 3.0 (native)) is attractive for > some git workflows. It means you

Re: tag2upload service architecture and risk assessment - draft v2

2019-08-29 Thread Raphael Hertzog
Hi, I reviewed the whole thread and the point of friction is the requirement to sign the .dsc file to make sure that the source package matches what the maintainer intended to upload. Ian doesn't want the maintainer to have to deal with the .dsc and the ftpmasters wants to have a signature within

Re: salsa.debian.org partially down

2019-08-16 Thread Raphael Hertzog
On Fri, 16 Aug 2019, Alexander Wirt wrote: > I am a bit surprised, from the first day on we said that there are limited > ressources for ci and that you should be nice to the service. Thats even > documented: > > "We mean that. Really. Be nice to the server. At some point in the future we >

Re: Git Packaging Round 1: Hopefully Easy Stuff

2019-08-16 Thread Raphael Hertzog
On Wed, 14 Aug 2019, Sam Hartman wrote: > Regardless of anything they are doing with Git, maintainers of a package > are expected to process patches sent to the BTS. Yes. > You cannot respond to a patch telling someone they need to file a merge > request to have it considered. I would not

Re: Git Packaging Round 1: Hopefully Easy Stuff

2019-08-16 Thread Raphael Hertzog
On Thu, 15 Aug 2019, Russ Allbery wrote: > Jonathan Carter writes: > > > The Debian QA DDPO pages will show you whether you have MRs on the same > > page where you see how many open bugs, RC bugs, lintian errors, etc you > > have. This makes it super easy to notice MRs when doing routine checks

Re: Building GTK programs without installing dconf-service?

2019-08-16 Thread Raphael Hertzog
On Fri, 16 Aug 2019, Simon McVittie wrote: > If there *is* consensus that "don't lose user configuration" is less > important than "weaken dependencies where possible", then that's a good > reason to weaken the dependency, although in practice that is likely to > be wontfix until

Re: salsa.debian.org partially down

2019-08-16 Thread Raphael Hertzog
Hi, On Fri, 16 Aug 2019, gregor herrmann wrote: > From what I know, this what not a "foolish user action" but an action > by a dedicated maintainer who enabled salsa-ci for all packages > ("projects") of a specific team; so they used a service advertised by > the salsa and salsa-ci teams. That

Re: Salsa.d.o: Please support the implementation request for a global config option to change the default for "Custom CI config path" in Gitlab

2019-08-11 Thread Raphael Hertzog
Hi, On Thu, 01 Aug 2019, Domenico Andreoli wrote: > >Questions to be answered: > >- Is the setting only a default applied to new projects? > >- If yes, how do you inform users that a new project with > > /.gitlab-ci.yml will not work? > >- If no, how do you inform users that an existing project

Re: Salsa.d.o: Please support the implementation request for a global config option to change the default for "Custom CI config path" in Gitlab

2019-07-25 Thread Raphael Hertzog
Hi, On Thu, 25 Jul 2019, Daniel Leidert wrote: > it has become quiet around this issue. So if you think such a configuration > option is useful too please support > > https://gitlab.com/gitlab-org/gitlab-ce/issues/41764 I added my +1. Another request that is important to have proper CI result

Re: git & Debian packaging sprint report

2019-07-22 Thread Raphael Hertzog
On Sun, 21 Jul 2019, Ian Jackson wrote: > IME as a sponsor I get (AFAICT) no mails as a result of my sponsorship > signatures so I think there are few automatic processes. That's actualy not true, dak is sending mails to the person who signs the upload when it has to send mails like NEW

Re: default firewall utility changes for Debian 11 bullseye

2019-07-16 Thread Raphael Hertzog
Hi, I'm replying to your questions but I have also other questions related to this fresh transition... On Tue, 16 Jul 2019, Arturo Borrero Gonzalez wrote: > as you may know, Debian 10 buster includes the iptables-nft utility by > default, > which is an iptables flavor that uses the nf_tables

Re: Could we generate d/control instead of working with "assembly level code" directly (was: Re: The noudeb build profile and dh-only rules files)

2019-07-09 Thread Raphael Hertzog
On Tue, 09 Jul 2019, Simon Richter wrote: > Your proposal of generating some of the fields doesn't affect the API > itself, as long as the fields are populated at the right time. We don't > have a mechanism for updating the control file at build time, because any > part of the build process that

Re: Question about Debian build infrastructure

2019-06-12 Thread Raphael Hertzog
On Wed, 12 Jun 2019, Vincent Bernat wrote: > It's https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=570623 > > Maintainer doesn't seem to be interested or have no time to consider the > patch since many years. Another sticking point with reprepro is the lack of Acquire-by-hash support:

Re: paying people for Debian work (Re: Why do we take so long to realise good ideas (Was: Difficult Packaging Practices))

2019-06-03 Thread Raphael Hertzog
Hi, On Mon, 03 Jun 2019, Paul Wise wrote: > There are a few things that are possibly concerning: Thanks for sharing those. Let me answer them. > Freexian is essentially the only available-to-hire provider of > services for Debian LTS, as the Freeside link doesn't lead anywhere > useful. This

Re: Why do we take so long to realise good ideas (Was: Difficult Packaging Practices)

2019-05-29 Thread Raphael Hertzog
On Wed, 29 May 2019, Ansgar wrote: > On Wed, 2019-05-29 at 10:38 +0200, Raphael Hertzog wrote: > > On Wed, 29 May 2019, Andrey Rahmatullin wrote: > > > One of the popular answers to this and some other problems is "nobody sat > > > down and wrote the code". Not

Re: Why do we take so long to realise good ideas (Was: Difficult Packaging Practices)

2019-05-29 Thread Raphael Hertzog
Hi, On Wed, 29 May 2019, Andrey Rahmatullin wrote: > One of the popular answers to this and some other problems is "nobody sat > down and wrote the code". Not sure what can we do about this class of > reasons. Use the $300,000 on our bank accounts?

Looking for a technical writer to update the Debian Handbook

2019-05-03 Thread Raphael Hertzog
Hello, Roland and I, the authors of the Debian Administrator's Handbook (package debian-handbook), we have not managed to update the book for Debian 9 and I don't want this to happen again for Debian 10 buster. I'm thus looking for a technical writer that would be willing to update the book for

Re: Handling of entropy during boot

2019-01-10 Thread Raphael Hertzog
Hi, On Wed, 09 Jan 2019, Theodore Y. Ts'o wrote: > Pointers, please? Let's see them and investigate. The primary issue > I've been aware of to date has been on Fedora systems, and it's due to > some Red Hat specific changes that they made for FEDRAMP compliance > --- and Red Hat has dealt with

Re: Sending using my @debian.org in gmail

2018-12-06 Thread Raphael Hertzog
Hi, On Tue, 04 Dec 2018, Marc Haber wrote: > >> If I could vote for which idea Debian mail admin time is dedicated > >> (which I cannot since Debian admins are volunteers and can choose what > >> to work on), I'd vote for better spam filtering on > >> @packages.debian.org and

Re: Upcoming Qt switch to OpenGL ES on arm64

2018-11-29 Thread Raphael Hertzog
Hello, On Thu, 29 Nov 2018, Adrian Bunk wrote: > Qt already supports runtime ES/non-ES in the same library build on > Windows [2], something like that might also be doable for Linux if > anyone (Linaro? Canonical?) with a real interest in that would work > on making it happen. > > Some of the

Re: Qt with GLES on arm64 maintainer's decision - Was:: Upcoming Qt switch to OpenGL ES on arm64

2018-11-26 Thread Raphael Hertzog
Hello Lisandro, TLDR: thank you for starting this discussion, it was required as it's not an easy decision to take as there is no realistic perfect solution, but I believe you took the wrong decision. Please consider deferring the decision to the technical committe by seeking his advice (point

Re: Upcoming Qt switch to OpenGL ES on arm64

2018-11-26 Thread Raphael Hertzog
Hello, On Sat, 24 Nov 2018, bret curtis wrote: > Moving Qt back to using Desktop GL from GLES is going to have zero > impact performance on the RPi since the VC4 supports up to OpenGL 2.1 > and and GLES 2.0 [1] That's a different claim to what you made in a former message. > The problem is that

Re: Upcoming Qt switch to OpenGL ES on arm64

2018-11-26 Thread Raphael Hertzog
Hi, On Fri, 23 Nov 2018, Dmitry Shachnev wrote: > According to config_help.txt [1], Qt uses ES2 by default on Windows. Interesting. > But as Lisandro says, such a change in Debian will break many packages > (which are currently broken on ARM only), so we are definitely not > considering it at

Re: Upcoming Qt switch to OpenGL ES on arm64

2018-11-26 Thread Raphael Hertzog
Hello Bret, On Sat, 24 Nov 2018, bret curtis wrote: > This is a very wrong assumption, the OpenGL on a RPi (all of them) is > hardware accelerated via the VC4 mesa driver by Eric Anholt which is > shipped, by default, on by Raspbian. It supports up to OpenGL 2.1 and > if you plan on having

Re: Confusing our users - who is supporting LTS?

2018-11-06 Thread Raphael Hertzog
On Sun, 28 Oct 2018, Wouter Verhelst wrote: > On Sun, Oct 28, 2018 at 01:14:13AM +, Ben Hutchings wrote: > > Debian can't afford to pay developers in general, and previous > > proposals to pay specific developers were not well received. > > That was over a decade ago. The circumstances at the

Re: Confusing our users - who is supporting LTS?

2018-10-24 Thread Raphael Hertzog
Hi, On Tue, 23 Oct 2018, Noah Meyerhans wrote: > The question > here was simply about discoverability. If you're a Debian user just > beginning exploration of public cloud alternatives, should we make it > easy for you to launch LTS instead of stable? I don't see any reason to make it hard, but

Re: Confusing our users - who is supporting LTS?

2018-10-23 Thread Raphael Hertzog
Hi Steve, On Tue, 23 Oct 2018, Steve McIntyre wrote: > So I'm worried that those of us who have *not* volunteered to support > LTS are being pressured into spending our time on it anyway. What can > we do to fix that? How/where do we clarify for our users (and > developers!) what LTS means, and

Re: epoch bump request for gnome-calculator

2018-09-27 Thread Raphael Hertzog
On Wed, 26 Sep 2018, Jeremy Bicha wrote: > So is it appropriate to bump an epoch in Debian to match an important > downstream's epoch? Yes. Precisely because there is collaboration between both sides on those packages. The attitude "we don't care of mistakes made by derivatives" is

Re: Limiting the size of installed changelogs

2018-09-14 Thread Raphael Hertzog
On Fri, 14 Sep 2018, Marc Haber wrote: > Has anybody gotten dpkg path-exclude to work? Yes. It's been a long time that I have not used it but the main problem is that to be effective the option must be used right from the start (i.e. already at the debootstrap stage) otherwise you have to

Re: Failed to create sbuild chroot for cross-compiling

2018-08-27 Thread Raphael Hertzog
Hi, On Sun, 26 Aug 2018, Holger Wansing wrote: > My intention was indeed, to do a source-only upload. But apparently > sbuild builds the binary package nevertheless, even when told to prepare > for a source-only upload. > > So the main point here is: don't use sbuild, it's the wrong tool for

Re: Failed to create sbuild chroot for cross-compiling

2018-08-25 Thread Raphael Hertzog
Hi Holger, On Sat, 25 Aug 2018, Holger Wansing wrote: > I need to get some debian-installer packages uploaded for s390x and mips. FTR, Holger is referring to packages which are built only on those architectures (and that can't be built on amd64). > Since I have no hardware for that archs, I

Re: salsa irker bot moved to ssl

2018-08-23 Thread Raphael Hertzog
Hi, On Thu, 23 Aug 2018, Alexander Wirt wrote: > > properties seems to be JSON data in a text field and it contains the > > IRC URI multiple times. > done, thanks. Please check in your settings if all is fine now. Looks good, thanks. Cheers, -- Raphaël Hertzog ◈ Debian Developer Support

Re: salsa irker bot moved to ssl

2018-08-23 Thread Raphael Hertzog
On Thu, 23 Aug 2018, Alexander Wirt wrote: > > A simple SQL update query would save us a lot of time. Thank you for > > considering it. > Sure, do you have the query? And please ensure not to affect bots > running on other networks. I don't have any gitlab instance where to make test so this is

Re: salsa irker bot moved to ssl

2018-08-22 Thread Raphael Hertzog
Hi, On Sun, 29 Jul 2018, Alexander Wirt wrote: > in the face of the current spam attacks I implemented CertFP for my > irker instance. I also updated the default irc link in gitlab. However, > it is possible that every project using the bot has to migrate the server > setting to ssl. So if you

Re: RFR: email about regressions [was: Dealing with ci.d.n for package regressions]

2018-05-24 Thread Raphael Hertzog
On Thu, 24 May 2018, Sebastiaan Couwenberg wrote: > None of the other QA tools mail the maintainer without them asking for > it, autopkgtest shouldn't either. With the exception of piuparts, none of them affect testing migration. Conversely, the autoremoval mails and the testing migration mails

Re: RFR: email about regressions [was: Dealing with ci.d.n for package regressions]

2018-05-24 Thread Raphael Hertzog
Hi Paul, On Wed, 23 May 2018, Paul Gevers wrote: > I have had a complaint about my e-mail, boiling down to it should be > opt-in. I am not fully convinced (as I fear too many package maintainers > will miss the fact their autopkgtest delays another package, but I want > to start sending the

Re: Firefox 60esr on Stretch ?

2018-05-11 Thread Raphael Hertzog
On Thu, 10 May 2018, Jonathan Dowland wrote: > On Wed, May 09, 2018 at 08:27:32PM +0200, Moritz Muehlenhoff wrote: > > It would be nice to move away from using RC bugs as testing blockers, > > but instead declare a source package as not suitable for stable (e.g. > > in some meta data on ftp-master

Re: [1/2] MBF: Defunct alioth addresses in the Maintainer: field (serious)

2018-05-10 Thread Raphael Hertzog
Hi, On Wed, 09 May 2018, Mathieu Parent (Debian) wrote: > I will probably request the (re-)creation of those two mailing lists > unless the team+s...@tracker.debian.org is ready to use. Raphael, what > is the status of this? Where is the doc? I just implemented it. There is no doc yet. But

Re: Firefox 60esr on Stretch ?

2018-05-09 Thread Raphael Hertzog
On Fri, 04 May 2018, Moritz Mühlenhoff wrote: > We should make it easy for administrators of bigger desktop > deployments to easily create debs for local deployments, but > keeping all those extensions in a stable release is just > broken and we should block them from testing migration. While I

Re: Please do not drop Python 2 modules

2018-05-02 Thread Raphael Hertzog
Hi, On Mon, 30 Apr 2018, Adrian Bunk wrote: > > So yes, LTS is fully part of the Debian project, and how Python 2.7 is > > supported should IMO very much be our concern. Now, we think that we > > should only support Python 2.7 for more than until Buster is EOL and > > becomes an LTS, I support

Re: RFC: Support for zstd in .deb packages?

2018-04-27 Thread Raphael Hertzog
Hello, On Fri, 27 Apr 2018, Guillem Jover wrote: > But in any case, I'm still open to data and opinions given that this > is in the end a matter of trade-offs, so → request for comments. :) I believe that the "zstd" compression format is providing an interesting trade-off compared to other

Re: Completed: lists.alioth.debian.org migration

2018-04-20 Thread Raphael Hertzog
Hi, On Fri, 20 Apr 2018, Christoph Biedl wrote: > On the other hand I fully agree doing dozens or hundreds of uploads just > because an address out of my control became invalid is a huge waste of > ressources that are better spent elsewhere. However, that's why > alioth-lists was created. We

Re: Completed: lists.alioth.debian.org migration

2018-04-19 Thread Raphael Hertzog
Hello, On Thu, 19 Apr 2018, Christoph Biedl wrote: > > Also, @lists.alioth.debian.org addresses that were *not* migrated now > > result in bounces as expected. Are there already plans for a MBF > > severity RC against all packages with a now-failing maintainer address? > > Following the rule a

Re: More expressive Multi-Arch field

2018-04-19 Thread Raphael Hertzog
Hello Lumin, On Wed, 18 Apr 2018, Lumin wrote: > Compared to "same"/"foreign", the idea above provides a more > expressive and self-doc'd Multi-Arch field. > > Your opinion? I think that you have no idea of the amount of energy and discussion that went into Multi-Arch. While your proposed

Re: Future of the Tryton suite in Debian

2018-04-09 Thread Raphael Hertzog
Hello Mathias, On Thu, 05 Apr 2018, Mathias Behrle wrote: > I don't plan to continue the maintenance of the Tryton suite in my *free* > time. :-( > The current evaluation of the situation shows unfortunately a different > result: > - After years of continued discussions and confrontations I

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

2018-03-22 Thread Raphael Hertzog
Hi, On Thu, 22 Mar 2018, Lars Wirzenius wrote: > I'm repeating myself, but could we please find another way to store > this information than in the source package? I'd like to see all of Sure. > I envision a service, metadata.debian.org, with a suitable > authenticated API to allow Debian

Re: Extended Long Term Support for Wheezy

2018-02-27 Thread Raphael Hertzog
Hi, On Mon, 26 Feb 2018, Peter Palfrader wrote: > > - for buildd/DSA teams, can we keep wheezy buildds (only amd64/i386 has > > been requested so far) for one year more? > > I don't think DSA is thrilled about committing to keep anything other > than amd64 for anything longer than was already

Re: Extended Long Term Support for Wheezy

2018-02-27 Thread Raphael Hertzog
On Mon, 26 Feb 2018, Bastian Blank wrote: > On Sun, Feb 25, 2018 at 09:54:27PM +0100, Raphael Hertzog wrote: > > Are you suggesting that it should be possible to store our own data > > in another git repository and that the tracker should be easily able to > > merge the

Re: Extended Long Term Support for Wheezy

2018-02-25 Thread Raphael Hertzog
On Sun, 25 Feb 2018, Moritz Mühlenhoff wrote: > The security tracker is fairly flexible and it should take little > effort to setup a separate instance which is based on the main > data/our triage efforts while acting on a local Packages file. > > Ideally document this process publicly, so that

Re: Extended Long Term Support for Wheezy

2018-02-22 Thread Raphael Hertzog
Hi, On Thu, 22 Feb 2018, Lars Wirzenius wrote: > I don't have an opinion on whether this should be done on Debian > servers or not, but I have a comment on providing security support for > more than a decade. How do you plan to deal with the kernel? FTR, I'm not involved in CIP and thus I can't

Re: Extended Long Term Support for Wheezy, CIP

2018-02-22 Thread Raphael Hertzog
Hello, On Thu, 22 Feb 2018, Geert Stappers wrote: > But what is "CIP"? > > My websearch did bring up "Clean In Place" and "Christelijk Intromatie > Platform" ... It was explained in my first mail. Civil Infrastructure Platform https://www.cip-project.org/ Cheers, -- Raphaël Hertzog ◈ Debian

Re: Extended Long Term Support for Wheezy

2018-02-22 Thread Raphael Hertzog
Hello, On Tue, 20 Feb 2018, Moritz Mühlenhoff wrote: > LTS has a clearly defined scope, while this is essentially contracting > work to extend the life time of some packages for some customers. > > I don't see a compelling reason for it to run on Debian infrastructure. This was also my first

Extended Long Term Support for Wheezy

2018-02-20 Thread Raphael Hertzog
[ Bcc to ftpmasters, wanna-build team, DSA team, LTS team, security team to catch their attention ] Hello, some of the LTS sponsors are looking to extend the support period of Debian 7 Wheezy (from a few months up to a full year). Some of the LTS sponsors (notably Plat'Home, Toshiba) are also

Re: What can Debian do to provide complex applications to its users?

2018-02-19 Thread Raphael Hertzog
On Mon, 19 Feb 2018, Samuel Thibault wrote: > Raphael Hertzog, on lun. 19 févr. 2018 15:19:59 +0100, wrote: > > On Fri, 16 Feb 2018, Jonathan Carter (highvoltage) wrote: > > > > - we could relax our requirements and have a way to document the > > > > limitations

Re: What can Debian do to provide complex applications to its users?

2018-02-19 Thread Raphael Hertzog
On Mon, 19 Feb 2018, Paul Wise wrote: > On Mon, Feb 19, 2018 at 9:51 PM, Raphael Hertzog wrote: > > > I don't want to lower the quality of what we have built so far, so while > > it's technically possible to build .deb and include a bundle of libraries > > pinned at the

Re: What can Debian do to provide complex applications to its users?

2018-02-19 Thread Raphael Hertzog
On Fri, 16 Feb 2018, Jonathan Carter (highvoltage) wrote: > > - we could relax our requirements and have a way to document the > > limitations of those packages (wrt our usual policies) > > Which requirements are you referring to? If it's relaxing the need for > source for minified javascript,

Re: What can Debian do to provide complex applications to its users?

2018-02-19 Thread Raphael Hertzog
On Sat, 17 Feb 2018, Russ Allbery wrote: > The reason why Debian in general doesn't like to support vendored source > is because of the security implications: when there's a security > vulnerability in one of the vendored libraries, updating the relevant > packages becomes a nightmare. It's a

Re: What can Debian do to provide complex applications to its users?

2018-02-19 Thread Raphael Hertzog
On Fri, 16 Feb 2018, W. Martin Borgert wrote: > Is was a relevant part of the problem mentioned in Raphaels bug > report: Minified JS libraries without source code. this was one > of the starting points of this discussion. (#890598) It's not "without source code", it's just that the source code

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

2018-02-19 Thread Raphael Hertzog
Hi, On Sat, 17 Feb 2018, Andreas Tille wrote: > > I know this, but this specific sub-thread was for the case if the team > > has gotten a list on lists.debian.org (so with public archives already). > > Using the tracker team for automated mail only is fine. > > I have something like ftpmaster

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

2018-02-17 Thread Raphael Hertzog
Hi, On Sat, 17 Feb 2018, Andreas Tille wrote: > On Fri, Feb 16, 2018 at 02:10:30PM +0100, Raphael Hertzog wrote: > > On Fri, 19 Jan 2018, Jeremy Bicha wrote: > > > 3. If a team manages to get a lists.debian.org address, it's > > > recommended that they s

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

2018-02-17 Thread Raphael Hertzog
Hello, On Tue, 26 Dec 2017, Mehdi Dogguy wrote: > For example, have a look at the following packages: > - https://tracker.debian.org/pkg/siridb-server > - https://tracker.debian.org/pkg/libcleri > > The maintainer box is not even shown. I guess this might be a bug to file > against

What can Debian do to provide complex applications to its users?

2018-02-16 Thread Raphael Hertzog
Hello everybody, the fact that I had to request the removal of dolibarr from Debian makes me sad (see below for the reasons) and I believe that we should be able to do better to provide complex applications to our end users. Dolibarr is not alone: - while gitlab is packaged in Debian, its

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

2018-02-16 Thread Raphael Hertzog
On Fri, 16 Feb 2018, Thibaut Paumard wrote: > Don't those two last paragraphs contradict each other? Or do you mean that > team subscribers will (still) receive only the automatic maintenance > e-mails? Yes, team subscribers receive only the automatic e-mails forwarded by the various services

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

2018-02-16 Thread Raphael Hertzog
Hi, On Fri, 19 Jan 2018, Jeremy Bicha wrote: > 3. If a team manages to get a lists.debian.org address, it's > recommended that they switch the Maintainer fields in their packages > from the Alioth list address to that address, right? It depends on your choice. But I would not recommend this. I

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

2018-02-14 Thread Raphael Hertzog
On Wed, 14 Feb 2018, Wouter Verhelst wrote: > Well, obviously, because 1:1.6 is larger than 1.8, according to our > versioning rules. > > I agree that the epoch not being in the file name makes that unexpected, > but that's a bug in whatever decides that filename, not in the use of > the epoch.

Re: Repackaging upstream source with file modifications?

2018-02-13 Thread Raphael Hertzog
Hi Colin, On Mon, 12 Feb 2018, Colin Watson wrote: > I considered just applying this as a patch in debian/patches/, but of > course that's still distributing the encumbered file in the > .orig.tar.xz, and Lintian just issues license-problem-non-free-RFC about > the patch file instead. (Again, I

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

2018-02-08 Thread Raphael Hertzog
On Thu, 08 Feb 2018, Ian Campbell wrote: > Is it also the case that today we implicitly require that all versions > used in a source package name's history are unique even once the epochs > are stripped off (e.g. a given $upstream-$debianrev must be unique and > not differ only in the epoch)? If

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

2018-02-07 Thread Raphael Hertzog
Hi, On Wed, 07 Feb 2018, Chris Lamb wrote: > Could you please file bugs for these issues? Many thanks. Done: - https://bugs.debian.org/889814 Improve long description of epoch-change-without-comment => Additional suggestions to put in the long description are welcome. -

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

2018-02-07 Thread Raphael Hertzog
Hi, On Tue, 06 Feb 2018, Chris Lamb wrote: > (The long description could make more scary noises about bumping, > however.) And include an explanation of when it's appropriate or not, and of ways to avoid it altogether... Please someone do it and add that to the auto-reject list. And also add a

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

2018-01-09 Thread Raphael Hertzog
Hello, On Thu, 04 Jan 2018, Adam Borowski wrote: > On Thu, Jan 04, 2018 at 01:01:15PM +0100, Raphael Hertzog wrote: > > I agree. I have plans to create email addresses like > > team+@tracker.debian.org that could be used for this purpose. > > The package tracker would au

Re: package mail aliases (was: salsa.debian.org)

2018-01-04 Thread Raphael Hertzog
On Tue, 26 Dec 2017, W. Martin Borgert wrote: > On 2017-12-26 14:48, Mattia Rizzolo wrote: > > That's now fixed, and you can use $pack...@packages.debian.org in the > > Maintainer field. > > Does $package need to be equal to the source or binary package name? source package name, please. > In

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

2018-01-04 Thread Raphael Hertzog
On Thu, 28 Dec 2017, Adam Borowski wrote: > On Thu, Dec 28, 2017 at 09:38:11AM -0500, Jeremy Bicha wrote: > > On Thu, Dec 28, 2017 at 7:37 AM, Ole Streicher wrote: > > > Question here is: how does the tracker identify which packages are team > > > maintained? Currently, this

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

2018-01-04 Thread Raphael Hertzog
Hello, On Tue, 26 Dec 2017, Boyuan Yang wrote: > 在 2017年12月26日星期二 CST 下午9:48:50,Mattia Rizzolo 写道: > > On Tue, Dec 26, 2017 at 02:45:38PM +0100, Marc Haber wrote: > > > The time before the last time I asked about tracker, the answer was > > > that this was not yet possible due to old lintian

Re: Team naming policy on salsa.debian.org

2018-01-02 Thread Raphael Hertzog
Hi, On Sun, 31 Dec 2017, Riku Voipio wrote: > On Tue, Dec 26, 2017 at 02:17:24PM +0100, Arturo Borrero Gonzalez wrote: > > Following with your example (pkg-suricata-team) I prefer to make it > > explicit for people outside debian that this is about packaging. > > So I usually put the 'pkg' string

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

2018-01-02 Thread Raphael Hertzog
On Thu, 28 Dec 2017, Marc Haber wrote: > On Tue, 26 Dec 2017 14:48:50 +0100, Mattia Rizzolo > wrote: > >On Tue, Dec 26, 2017 at 02:45:38PM +0100, Marc Haber wrote: > >> The time before the last time I asked about tracker, the answer was > >> that this was not yet possible due

Re: Alioth: the future of mailing lists

2017-10-31 Thread Raphael Hertzog
Hi, On Sun, 22 Oct 2017, Marc Haber wrote: > On Wed, 20 Sep 2017 10:31:16 +0200, Raphael Hertzog > <hert...@debian.org> wrote: > >The only thing we are waiting currently > >for is a lintian upload where #871575 [3] is fixed (and then we need the > >backport

Re: Alioth: the future of mailing lists

2017-09-20 Thread Raphael Hertzog
Hi, On Tue, 19 Sep 2017, Wouter Verhelst wrote: > > Instead we should use @packages.debian.org. But for this we > > need a lintian upload and a lintian backport to be installed on > > ftp-master: > > Er, that would create a mail loop. @packages.debian.org > redirects to the data of the

Re: Alioth: the future of mailing lists

2017-09-19 Thread Raphael Hertzog
Hi, On Mon, 18 Sep 2017, Vincent Bernat wrote: > Would any of those solutions also email the uploaders or recent people > in d/changelog? This would be helpful for NMU as well as for > team-maintained packages in a large team. No, not yet. But in both cases, it's a matter of adding code to the

Re: Alioth: the future of mailing lists

2017-09-18 Thread Raphael Hertzog
Hi, On Mon, 18 Sep 2017, Paul Wise wrote: > If the Maintainer field is going to be completely deterministic based > on the package name, we should probably just change dak/BTS/etc to > mail those addresses instead of making dak put those addresses in > Maintainer fields in Sources/Packages or

Re: Alioth: the future of mailing lists

2017-09-18 Thread Raphael Hertzog
Hello Axel, On Mon, 18 Sep 2017, Axel Beckert wrote: > Alexander Wirt wrote: > > - Distribution lists for use in the Maintainer: field. We suggest > > that, with maybe some extra code, this use-case could be well served > > by the tracker.debian.org service for almost all purposes. >

Re: X facts about Debian - some fact checking and looking for ideas.

2017-09-01 Thread Raphael Hertzog
Hi, On Thu, 24 Aug 2017, shirish शिरीष wrote: > As far as fact-checking goes, can anybody share about Debian and Kali > Linux relationship in bit more detail. AFAIK Raphaël Hertzog is one of > the main developers and there has been lot of symbiotic relationship > between the two projects but how

Re: OpenSSL disables TLS 1.0 and 1.1

2017-08-22 Thread Raphael Hertzog
On Thu, 17 Aug 2017, Philipp Kern wrote: > At the same time holding testing hostage does not feel right to me. I > applaud the intention, but I strongly dislike the implementation. +1 Also in the security field (i.e. for Kali Linux as derivative based on Testing), we like to keep support for

Un mainteneur pour gcompris?

2017-08-18 Thread Raphael Hertzog
Bonjour, ca serait super si on pouvait trouver quelqu'un pour maintenir le paquet gcompris-qt dans Debian... Yann Dirson ne s'en occupe plus: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=826428 Idéalement il faudrait aussi que gcompris-qt remplace officiellement gcompris... ce n'est pas

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

2017-08-10 Thread Raphael Hertzog
Hi, On Wed, 09 Aug 2017, Christian Seiler wrote: > Speaking of: are there any good introductions for AppArmor? Not > necessarily for me personally (I've had some experience with > SELinux, so I recon I'll figure AppArmor out easily enough), but > for beginners? Something I can point friends of

Re: Maintainer information in source packages (was: Re: Returning to the requirement that Uploaders: contain humans)

2017-08-09 Thread Raphael Hertzog
Hello, On Fri, 04 Aug 2017, Ansgar Burchardt wrote: > So I have been wondering several times whether we should move the > maintainer information elsewhere. For example, tracker.d.o could be > extended to record maintainer information. It could also understand > the concept of "teams" listing

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

2017-05-16 Thread Raphael Hertzog
On Mon, 15 May 2017, Adrian Bunk wrote: > The contents of the Gentoo homepage is similar to what Debian has but > presented with a different CSS - something like that would be a good > improvement. I took a look at the Gentoo website and there's more than just better CSS. I find it much better

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

2017-03-27 Thread Raphael Hertzog
On Mon, 27 Mar 2017, Thibaut Paumard wrote: > Thanks for the pointer. Just out of curiosity, do you intend on using > the blends framework for the pkg-security team? This is not part of any current plan but I have no objection if someone wants to do the required work. > If you have pointers

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

2017-03-25 Thread Raphael Hertzog
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 to merge back packages useful for penetration testers into Debian. The benefit is clear for that

Re: Reprepro ? [WAS Personnalisation de l'installateur debian : suite]

2017-01-26 Thread Raphael Hertzog
Salut, On Thu, 26 Jan 2017, Laurent COOPER wrote: > Face à la difficulté de gérer le fichier Release pour intégrer le sha256 > des images debian, j'ai été brutal mais efficace : > > J'ai supprimé le check du hash dans la méthode wget de simple-cdd et il > saute cette étape qui n'était pas

Re: Reprepro ? [WAS Personnalisation de l'installateur debian : suite]

2017-01-26 Thread Raphael Hertzog
On Thu, 26 Jan 2017, Laurent COOPER wrote: > cela veut il dire que pour les dépôts officiels debian, les sommes de > contrôles dans le fichier Release sont gérées à la main ? Si c'est le Non, les dépôts officiels sont gérés avec "dak". reprepro n'a pas toutes les fonctionnalités de dak. > cas,

Re: Reprepro ? [WAS Personnalisation de l'installateur debian : suite]

2017-01-26 Thread Raphael Hertzog
Salut, On Wed, 25 Jan 2017, Laurent COOPER wrote: > Je vois bien une ligne du type > 9ecaf703beaa8d2a5aff44c581162a9b72131 > main/installer-amd64/20150422+deb8u4+b2/images/SHA256SUMS > > Mais dans mon Release, je n'ai rien d'équivalent. > > Comment puis je parler gentiment à Reprepro pour

Re: Feedback on 3.0 source format problems

2017-01-12 Thread Raphael Hertzog
Hi, On Sun, 01 Jan 2017, Guillem Jover wrote: > On Sun, 2017-01-01 at 10:47:59 -0800, Nikolaus Rath wrote: > > On Jan 01 2017, Guillem Jover wrote: > > > (I'm not using because > > > TBH it read more like a sales brochure than a

Re: Converting to dgit

2017-01-12 Thread Raphael Hertzog
Hi, On Fri, 06 Jan 2017, Ghislain Vaillant wrote: > > I don't use it often enough to remember all the details either. I don't > > recall the last time I had to do more than copy/paste a command from the > > man > > page (OK, git-dpm tag I can remember). > > Besides, git-dpm usually tells you

Looking for new maintainer(s) for net-snmp

2016-12-02 Thread Raphael Hertzog
Hello everybody, the net-snmp source package is looking for a new maintainer: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835654 It is currently affected by 3 release critical bugs and has many reverse dependencies so it really needs to be well maintained. Uptsream seems to be reasonably

Re: about build flavours

2016-11-29 Thread Raphael Hertzog
Hello, On Tue, 29 Nov 2016, Arturo Borrero Gonzalez wrote: > Currently, our main idea is to create a suricata-hyperscan package > which includes the dependency to hyperscan, and the binary is build > linked to the library. > > We distribute two /usr/bin/suricata binaries in two binary packages:

Re: Debian Installer Stretch Alpha 8 release

2016-11-21 Thread Raphael Hertzog
On Mon, 21 Nov 2016, Guillem Jover wrote: > Oh, and forgot to mention, this issue has been known for over 8 > months, and now there's this need to be pushy and rush things, etc. > I certainly do not appreciate that. I have not been involved in this project so I don't know its history but #843073

Re: Debian Installer Stretch Alpha 8 release

2016-11-21 Thread Raphael Hertzog
Hello Guillem, On Mon, 14 Nov 2016, Michael Biebl wrote: > Just for the record: I can confirm it fixes the problem in dpkg-shlibdeps. [...] > Guillem, it would be great if you can upload a fixed dpkg soon. A full week went by already. What's your plan? I can offer to upload dpkg 1.18.15.1 to

Re: DEP 8: Gathering Django usage analytics

2016-11-18 Thread Raphael Hertzog
Hi, On Fri, 18 Nov 2016, Lars Wirzenius wrote: > I'd rather not debate this on github. It's a proprietary system, and > effectively a web forum I'd need to keep polling to see if there's You get mail notifications on GitHub too. > responses. Further, that response paints me either as someone

Re: [buildd-tools-devel] Bug#843773: misleading timestamps in binnmus

2016-11-16 Thread Raphael Hertzog
Hi, On Mon, 14 Nov 2016, Johannes Schauer wrote: > > Can I ask you the converse question: what same-timestamp proposal do > > you think is best and why ? > > I found Guillem's suggestion the most sensible and as far as I understand the > matter also the easiest to implement: > > Quoting Guillem

  1   2   3   4   5   6   7   8   9   10   >