Bug#820460: reprepro: Omitting Release from DebIndices still generates that file

[Frédéric Brière]

reopen 820460 
notfixed 820460 5.1.0-1
thanks


I'm still getting the same behavior with 5.1.1-1:

  $ grep DebIndices conf/distributions 
  DebIndices: Packages . .gz .xz
  DebIndices: Packages . .gz .xz
  DebIndices: Packages . .gz .xz
  DebIndices: Packages . .gz .xz
  $ find -name '*Release*' | xargs rm
  $ reprepro export
  $ find -name Release | wc -l
  4

Bug#820460: reprepro: Omitting Release from DebIndices still generates that file

[Frédéric Brière]

package reprepro
tags 820460 -moreinfo +patch
thanks

On Sun, Apr 10, 2016 at 12:11:16PM +0200, Bernhard R. Link wrote:
> * Frédéric Brière  [160408 18:51]:
> > Release files are still generated, despite having
> > "DebIndices: Packages . .gz .xz" in my configuration.
> 
> That file should no longer be generated, but reprepro will not delete an
> old file if it is still there. Could you check if it is newly generated
> or just the old file?

They are recreated every time.

If I understand correctly, the solution is merely to not pass a default
filename to exportmode_init(), right?  (This does result in the *release
argument no longer being used anywhere, though.)

diff --git a/distribution.c b/distribution.c
index 91a31a0..46d0bcb 100644
--- a/distribution.c
+++ b/distribution.c
@@ -226,12 +226,12 @@ CFstartparse(distribution) {
 		(void)distribution_free(n);
 		return r;
 	}
-	r = exportmode_init(>deb, true, "Release", "Packages");
+	r = exportmode_init(>deb, true, NULL, "Packages");
 	if (RET_WAS_ERROR(r)) {
 		(void)distribution_free(n);
 		return r;
 	}
-	r = exportmode_init(>dsc, false, "Release", "Sources");
+	r = exportmode_init(>dsc, false, NULL, "Sources");
 	if (RET_WAS_ERROR(r)) {
 		(void)distribution_free(n);
 		return r;

Bug#820460: reprepro: Omitting Release from DebIndices still generates that file

[Bernhard R. Link]

package reprepro
tags 820460 +moreinfo
thanks

* Frédéric Brière  [160408 18:51]:
> The documentation for DebIndices states that omitting the optional
> Release filename will result in no file being generated.  This does not
> appear to work for me; Release files are still generated, despite having
> "DebIndices: Packages . .gz .xz" in my configuration.

That file should no longer be generated, but reprepro will not delete an
old file if it is still there. Could you check if it is newly generated
or just the old file?


Bernhard R. Link
-- 
F8AC 04D5 0B9B 064B 3383  C3DA AFFC 96D1 151D FFDC

Bug#820460: reprepro: Omitting Release from DebIndices still generates that file

[Frédéric Brière]

Package: reprepro
Version: 4.17.0-1
Severity: normal

The documentation for DebIndices states that omitting the optional
Release filename will result in no file being generated.  This does not
appear to work for me; Release files are still generated, despite having
"DebIndices: Packages . .gz .xz" in my configuration.


-- System Information:
Debian Release: stretch/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.4.0-1-amd64 (SMP w/3 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages reprepro depends on:
ii  libarchive13 3.1.2-11+b1
ii  libbz2-1.0   1.0.6-8
ii  libc62.22-5
ii  libdb5.3 5.3.28-11
ii  libgpg-error01.21-2
ii  libgpgme11   1.6.0-1
ii  liblzma5 5.1.1alpha+20120614-2.1
ii  pinentry-curses  0.9.7-5
ii  zlib1g   1:1.2.8.dfsg-2+b1

Versions of packages reprepro recommends:
ii  apt  1.2.10

Versions of packages reprepro suggests:
ii  gnupg-agent  2.1.11-6
pn  inoticoming  
pn  lzip 

-- no debconf information