Quantcast

132 packages with several sources for stretch in the archive… (Re: Bug#860608: [pkg-golang-devel] Bug#860608: golang: FTBFS: Go version is "go1.6.1", ignoring -next /<<PKGBUILDDIR>>/api/next.txt)

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

132 packages with several sources for stretch in the archive… (Re: Bug#860608: [pkg-golang-devel] Bug#860608: golang: FTBFS: Go version is "go1.6.1", ignoring -next /<<PKGBUILDDIR>>/api/next.txt)

Holger Levsen-2
On Fri, Apr 21, 2017 at 01:00:20PM +0200, Lucas Nussbaum wrote:
> FYI, that's the number of additional copies of source packages in
> stretch, per source package:
>
> udd=> select source, count(*) from sources where release='stretch' and
> component='main' and extra_source_only group by source order by count
> desc;
[...]
> (132 rows)

that's quite astounding (to me) and IMHO also quite bad… can we do something
to fix this for Buster at least?

reply-to: set to debian-devel@…


--
cheers,
        Holger

signature.asc (828 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Bug#860608: Info received (132 packages with several sources for stretch in the archive… (Re: Bug#860608: [pkg-golang-devel] Bug#860608: golang: FTBFS: Go version is "go1.6.1", ignoring -next /<<PKGBUILDDIR>>/api/next.txt))

Debian Bug Tracking System
Thank you for the additional information you have supplied regarding
this Bug report.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
 Go Compiler Team <[hidden email]>

If you wish to submit further information on this problem, please
send it to [hidden email].

Please do not send mail to [hidden email] unless you wish
to report a problem with the Bug-tracking system.

--
860608: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860608
Debian Bug Tracking System
Contact [hidden email] with problems

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: 132 packages with several sources for stretch in the archive… (Re: Bug#860608: [pkg-golang-devel] Bug#860608: golang: FTBFS: Go version is "go1.6.1", ignoring -next /<<PKGBUILDDIR>>/api/next.txt)

Paul Gevers-4
In reply to this post by Holger Levsen-2
Hi,

On 21-04-17 13:29, Holger Levsen wrote:

> On Fri, Apr 21, 2017 at 01:00:20PM +0200, Lucas Nussbaum wrote:
>> FYI, that's the number of additional copies of source packages in
>> stretch, per source package:
>>
>> udd=> select source, count(*) from sources where release='stretch' and
>> component='main' and extra_source_only group by source order by count
>> desc;
> [...]
>> (132 rows)
>
> that's quite astounding (to me) and IMHO also quite bad… can we do something
> to fix this for Buster at least?
I don't think this number is bad per-se (assuming this extra_source_only
just meant it has "Build-Using"). The bad thing in my opinion is when
multiple version are kept around for a long time. I use this Build-Using
in multiple of my package, exactly to be able for this kind of analysis
(and in the end I hope globally fixing per release with (binNMU)
rebuilding).

Paul


signature.asc (499 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: 132 packages with several sources for stretch in the archive… (Re: Bug#860608: [pkg-golang-devel] Bug#860608: golang: FTBFS: Go version is "go1.6.1", ignoring -next /<<PKGBUILDDIR>>/api/next.txt)

Holger Levsen-2
On Fri, Apr 21, 2017 at 01:44:40PM +0200, Paul Gevers wrote:
> I don't think this number is bad per-se (assuming this extra_source_only
> just meant it has "Build-Using"). The bad thing in my opinion is when
> multiple version are kept around for a long time.

I consider the life time of stretch to be long, you don't?

Are security updates supposed to be build using the most current source
package in stretch or the one specified in "Build-Using"?


--
cheers,
        Holger

signature.asc (828 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: 132 packages with several sources for stretch in the archive… (Re: Bug#860608: [pkg-golang-devel] Bug#860608: golang: FTBFS: Go version is "go1.6.1", ignoring -next /<<PKGBUILDDIR>>/api/next.txt)

Paul Gevers-4
Hi,

On 21-04-17 14:10, Holger Levsen wrote:
> On Fri, Apr 21, 2017 at 01:44:40PM +0200, Paul Gevers wrote:
>> I don't think this number is bad per-se (assuming this extra_source_only
>> just meant it has "Build-Using"). The bad thing in my opinion is when
>> multiple version are kept around for a long time.
>
> I consider the life time of stretch to be long, you don't?

Oh, sure, but what I meant is during preparation of a release. If during
the freeze rebuilds are done, you only have the version that you ship
anyways.

> Are security updates supposed to be build using the most current source
> package in stretch or the one specified in "Build-Using"?

The version in Build-Using is added during building. So this field is
updated during security builds to the latest version. The Build-Depends
field determines (as always) which packages (potentially with version)
to use for building. Nothing new here.

Paul


signature.asc (499 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: 132 packages with several sources for stretch in the archive… (Re: Bug#860608: [pkg-golang-devel] Bug#860608: golang: FTBFS: Go version is "go1.6.1", ignoring -next /<<PKGBUILDDIR>>/api/next.txt)

Lucas Nussbaum-4
On 21/04/17 at 14:15 +0200, Paul Gevers wrote:

> Hi,
>
> On 21-04-17 14:10, Holger Levsen wrote:
> > On Fri, Apr 21, 2017 at 01:44:40PM +0200, Paul Gevers wrote:
> >> I don't think this number is bad per-se (assuming this extra_source_only
> >> just meant it has "Build-Using"). The bad thing in my opinion is when
> >> multiple version are kept around for a long time.
> >
> > I consider the life time of stretch to be long, you don't?
>
> Oh, sure, but what I meant is during preparation of a release. If during
> the freeze rebuilds are done, you only have the version that you ship
> anyways.
>
> > Are security updates supposed to be build using the most current source
> > package in stretch or the one specified in "Build-Using"?
>
> The version in Build-Using is added during building. So this field is
> updated during security builds to the latest version. The Build-Depends
> field determines (as always) which packages (potentially with version)
> to use for building. Nothing new here.

Note that it's "Built-Using", not "Build-Using", so it's really a
statement about the produced binary package, not an alternative way to
specify build-dependencies.

Lucas

Loading...