Your message dated Thu, 9 Jun 2016 15:49:46 +0200
with message-id <[email protected]>
and subject line Re: [buildd-tools-devel] Bug#826847: sbuild: override default 
debootstap's /etc/apt/sources.list
has caused the Debian Bug report #826847,
regarding sbuild: override default debootstap's /etc/apt/sources.list
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
826847: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=826847
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: sbuild
Version: 0.65.2-1
Severity: normal
User: [email protected]
Usertags: infomaniak.com-packaging

Hi there,

I am setting up an internal buildd (with no wanna-build) following:

  <https://wiki.debian.org/BuilddSetup>
  <https://wiki.debian.org/sbuild>

As we plan to recompile official Debian packages from internal Git
repositories, we do not mirror the source architecture, no need to waste
bandwidth and disk space:

  <https://www.debian.org/mirror/size>

I do not understand why sbuild-createchroot completely replaces the
${target}/etc/apt/sources.list generated by debootstrap with its own,
since the following commit:

  commit 7eaa13539e6542f553efbf81c2514cbfad2cbac8
  Author: Roger Leigh <[email protected]>
  Date:   Sun Jul 27 13:54:19 2008 +0100

    [sbuild-createchroot] Set up sources.list with --components values

So, my questions are:

1) what is the rationale for the current behavior, i.e. why not leaving
   all the *default* APT sources to debootstrap?

2) why adding by default deb-src for a *building* environment?  This
   seems quite strange to me, but I am sure I am missing something...

Thx, bye,
Gismo / Luca

-- System Information:
Debian Release: 8.5
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.18.30-imu (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages sbuild depends on:
ii  adduser         3.113+nmu3
ii  apt-utils       1.0.9.8.3
ii  libsbuild-perl  0.65.2-1
ii  perl            5.20.2-3+deb8u5

Versions of packages sbuild recommends:
ii  debootstrap  1.0.67
ii  fakeroot     1.20.2-1

Versions of packages sbuild suggests:
pn  deborphan  <none>
ii  wget       1.16-1

-- no debconf information

-- 
Luca Capello
Administrateur GNU/Linux

Infomaniak Network SA

Attachment: signature.asc
Description: Digital signature


--- End Message ---
--- Begin Message ---
tags 826847 + wontfix
thanks

Hi Raphaƫl,

On Thu, 09 Jun 2016 15:08:23 +0200, Raphael Hertzog wrote:
> On Thu, 09 Jun 2016, Luca Capello wrote:
> > 2) why adding by default deb-src for a *building* environment?  This
> >    seems quite strange to me, but I am sure I am missing something...
> 
> This could be explained by the desire to have "apt-get source" and
> "apt-get build-dep" working. In particular since sbuild allows "sbuild
> foo" with foo just a package name...

Thank you, I missed that "apt-get build-dep" requires deb-src.

And for "apt-get source" I forgot that by default sbuild builds binary
packages, which means that the sources could already be in the archive.

Tagging the bug as wontfix (not really a bug) and closing it, thank you
for the explanation.  I have just added the sources to our internal APT
mirror ;-)

Thx, bye,
Gismo / Luca

-- 
Luca Capello
Administrateur GNU/Linux

Infomaniak Network SA

Attachment: signature.asc
Description: Digital signature


--- End Message ---

Reply via email to