Skip Menu |

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the Log-Saftpresse CPAN distribution.

Report information
The Basics
Id: 110957
Status: resolved
Priority: 0/
Queue: Log-Saftpresse
People
Owner: Nobody in particular
Requestors: quanah.gibsonmount [...] gmail.com
Cc:
AdminCc:
Bug Information
Severity: (no value)
Broken in: 1.3
Fixed in: (no value)

History Show all quoted text
  Wed Jan 06 18:15:46 2016 quanah.gibsonmount [...] gmail.com - Ticket created
Subject: Remove debian/ dir from distribution
It is a violation of debian policy to include a debian/ directory with upstream source. Please fix your release process to remove this directory when creating the release tarball.
  Wed Jan 06 18:18:47 2016 quanah.gibsonmount [...] gmail.com - Correspondence added
On Wed Jan 06 18:15:46 2016, MISHIKAL wrote: Show quoted text
> It is a violation of debian policy to include a debian/ directory with > upstream source. Please fix your release process to remove this > directory when creating the release tarball.
See also https://wiki.debian.org/UpstreamGuide#Initial_Packaging
  Thu Jan 07 03:36:28 2016 BENNING [...] cpan.org - Correspondence added
Am Mi 06. Jan 2016, 18:18:47, MISHIKAL schrieb: Show quoted text
> On Wed Jan 06 18:15:46 2016, MISHIKAL wrote:
> > It is a violation of debian policy to include a debian/ directory with > > upstream source. Please fix your release process to remove this > > directory when creating the release tarball.
> > See also https://wiki.debian.org/UpstreamGuide#Initial_Packaging
I know, but there seems to be little intresst in including my packages at Debian. I tried to find a mentor/sponsor for the mtpolicyd package, but failed. Building the package from native format allows me to generate the changelog from Dist::Zilla. Thats the simplest way to build the packages for me.
  Thu Jan 07 03:36:29 2016 The RT System itself - Status changed from 'new' to 'open'
  Thu Jan 07 03:38:02 2016 BENNING [...] cpan.org - Status changed from 'open' to 'resolved'
  Fri Jan 08 00:18:41 2016 quanah.gibsonmount [...] gmail.com - Correspondence added
On Thu Jan 07 03:36:28 2016, BENNING wrote: Show quoted text
> Am Mi 06. Jan 2016, 18:18:47, MISHIKAL schrieb:
> > On Wed Jan 06 18:15:46 2016, MISHIKAL wrote:
> > > It is a violation of debian policy to include a debian/ directory > > > with > > > upstream source. Please fix your release process to remove this > > > directory when creating the release tarball.
> > > > See also https://wiki.debian.org/UpstreamGuide#Initial_Packaging
> > I know, but there seems to be little intresst in including my packages > at Debian. > I tried to find a mentor/sponsor for the mtpolicyd package, but > failed. > Building the package from native format allows me to generate the > changelog from Dist::Zilla. Thats the simplest way to build the > packages for me.
This has nothing to do with whether or not Debian distributes it. There may be other individuals or projects that *do* want to distribute it, and having the debian/ dir in the release tarball's a problem. That is part of why the policy exists. Again, please remove it.
  Fri Jan 08 00:18:42 2016 quanah.gibsonmount [...] gmail.com - Status changed from 'resolved' to 'open'
  Fri Jan 08 01:49:01 2016 SREZIC [...] cpan.org - Correspondence added
On 2016-01-08 00:18:41, MISHIKAL wrote: Show quoted text
> On Thu Jan 07 03:36:28 2016, BENNING wrote:
> > Am Mi 06. Jan 2016, 18:18:47, MISHIKAL schrieb:
> > > On Wed Jan 06 18:15:46 2016, MISHIKAL wrote:
> > > > It is a violation of debian policy to include a debian/ directory > > > > with > > > > upstream source. Please fix your release process to remove this > > > > directory when creating the release tarball.
> > > > > > See also https://wiki.debian.org/UpstreamGuide#Initial_Packaging
> > > > I know, but there seems to be little intresst in including my > > packages > > at Debian. > > I tried to find a mentor/sponsor for the mtpolicyd package, but > > failed. > > Building the package from native format allows me to generate the > > changelog from Dist::Zilla. Thats the simplest way to build the > > packages for me.
> > > This has nothing to do with whether or not Debian distributes it. > There may be other individuals or projects that *do* want to > distribute it, and having the debian/ dir in the release tarball's a > problem. That is part of why the policy exists. Again, please remove > it.
If I may chime in: the Debian policy mentions "rough /debian directory". I would interpret this that a "polished" directory is fine. Anyway, I also find it curious that the existence of this directory is objected even if the software is not packaged by debian at all... loosening the policy for these situations is probably a good idea.
  Fri Jan 08 14:47:53 2016 rt.cpan [...] sartak.org - Correspondence added
RT-Send-CC: ich [...] markusbenning.de
Hi Markus, Quanah, and others, I'm Shawn, one of the rt.cpan.org administrators. We had an outage today, and one mail that fell through the cracks was on this ticket. It was from ich@markusbenning.de and follows. I'm sorry about the disruption, Shawn On 2016-01-08 06:18, Quanah Gibson-Mount via RT wrote: Show quoted text
> Queue: Log-Saftpresse > Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=110957 > > > On Thu Jan 07 03:36:28 2016, BENNING wrote:
>> Am Mi 06. Jan 2016, 18:18:47, MISHIKAL schrieb:
>> > On Wed Jan 06 18:15:46 2016, MISHIKAL wrote:
>> > > It is a violation of debian policy to include a debian/ directory >> > > with >> > > upstream source. Please fix your release process to remove this >> > > directory when creating the release tarball.
>> > >> > See also https://wiki.debian.org/UpstreamGuide#Initial_Packaging
>> >> I know, but there seems to be little intresst in including my packages >> at Debian. >> I tried to find a mentor/sponsor for the mtpolicyd package, but >> failed. >> Building the package from native format allows me to generate the >> changelog from Dist::Zilla. Thats the simplest way to build the >> packages for me.
> > This has nothing to do with whether or not Debian distributes it. > There may be other individuals or projects that *do* want to > distribute it, and having the debian/ dir in the release tarball's a > problem. That is part of why the policy exists. Again, please remove > it.
Its just the most pragmatic way to create debian packages for me. Since the packages are not distributed with Debian its okay for me in this case to not comply with the policy. If a Debian Maintainer is willed to sponsor the package i would happyly switch to the quilt format and split upstream/packaging. Is this a theoretical discussion or is this causing real problems? Markus -- https://markusbenning.de/
  Mon Jan 11 18:50:53 2016 quanah.gibsonmount [...] gmail.com - Correspondence added
Show quoted text
> Its just the most pragmatic way to create debian packages for me. > Since the packages are not distributed with Debian its okay for me > in this case to not comply with the policy. > > If a Debian Maintainer is willed to sponsor the package i would > happyly > switch to the quilt format and split upstream/packaging. > > Is this a theoretical discussion or is this causing real problems?
It can cause real problems for other people who may want to package this. And I may want to package it in Zimbra as a replacement for pflogsumm. The point of not including debian/ dirs in the release tarballs is that other packages (such as myself) have their debian/ dirs that are specific to the package overwritten by your debian dir. Yes, it is trivial to work around that, but this is part of why the policy exists. Whether or not your package is currently picked up by debian, it really shouldn't include a debian/ dir with releases.
  Tue Jan 12 03:19:39 2016 ich [...] markusbenning.de - Correspondence added
Subject: Re: [rt.cpan.org #110957] Remove debian/ dir from distribution
Date: Tue, 12 Jan 2016 09:19:17 +0100
To: bug-Log-Saftpresse [...] rt.cpan.org
From: "Benning, Markus" <ich [...] markusbenning.de>
On 2016-01-12 00:50, Quanah Gibson-Mount via RT wrote: Show quoted text
> Queue: Log-Saftpresse > Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=110957 > > >
>> Its just the most pragmatic way to create debian packages for me. >> Since the packages are not distributed with Debian its okay for me >> in this case to not comply with the policy. >> >> If a Debian Maintainer is willed to sponsor the package i would >> happyly >> switch to the quilt format and split upstream/packaging. >> >> Is this a theoretical discussion or is this causing real problems?
> > It can cause real problems for other people who may want to package > this. And I may want to package it in Zimbra as a replacement for > pflogsumm. The point of not including debian/ dirs in the release > tarballs is that other packages (such as myself) have their debian/ > dirs that are specific to the package overwritten by your debian dir. > Yes, it is trivial to work around that, but this is part of why the > policy exists. Whether or not your package is currently picked up by > debian, it really shouldn't include a debian/ dir with releases.
Okay, if its really stands in your way for your packaging work, then its a valid reason. I just removed the debian folder from the upstream repository. I'll setup a seperate repository for debian packaging managed by git-buildpackage. Markus -- https://markusbenning.de/
  Sun May 15 05:10:00 2016 BENNING [...] cpan.org - Correspondence added
resolved?
  Sun May 15 05:10:02 2016 BENNING [...] cpan.org - Status changed from 'open' to 'resolved'