Re: For those who care about their packages in Ubuntu
On 1/18/06, Mike Bird <mgb-debian@yosemite.net> wrote:
> On Wed, 2006-01-18 at 05:29, Reinhard Tartler wrote:
> > Oh. There might be a misunderstanding: No binary package is taken from
> > debian, only source packages. This means that EVERY package is being
> > rebuilt in ubuntu on buildds, including arch: all packages. The output
> > of apt-cache shows the field 'Origin' to indicate that this is not a
> > package built on debian systems.
>
> Ubuntu does NOT set the origin in its packages:
>
> # dpkg -s dpkg | egrep -i '(origin|version):'
> Origin: debian
> Version: 1.13.10ubuntu4
> #
>
> apt can be a useful tool but it tells you where it knows a package
> can be found, not the actual origin of an installed package:
>
> # dpkg -i --force-all xli_1.17.0-18sarge1_i386.deb
> (snip)
> # apt-cache show xli | grep -i origin:
> Origin: Ubuntu
> #
I think this is something we can work on or have changed. I only
checked the output of apt-cache. I think apt-cache however, is the
most common case for user who want to know about a package, but
anyhow..
> > If I understand your proposal correctly, you propose to introduce
> > binNMU like versioning on ALL nondiverged packages (again, the source
> > package is identical!). This seem not feasible because of practical
> > problems.
>
> What practical problems? DDs can increment the two-dot version
> on a binary NMU. Why can't Ubuntu's copy-sources-from-debian
> script do the same?
requesting binNMUs requires access to wanna-build, AFAIK. Humble
ubuntu developers do not have access to that, just uploads. We can
talk about uploading policy. I ask to be corrected if I'm wrong on
this point.
> > btw, the 'buildX' packages do change the source package, but by
> > policy, only debian/changelog is touched, to increase the version
> > number of the package.
>
> What please is the difference between a buildX package and all the
> other packages that were rebuilt without the buildX annotation?
It is quite similar to what debian calls a binary NMU, but developers
do not need wanna-build access to that. Instead, they upload a new
.dsc and .diff.gz, which gets accepted by katie as new package upload.
These kind of uploads are necessary during transitions, e.g. when a
package has been built against an older library but needs to be
rebuilt with an newer one.
--
regards,
Reinhard
Reply to: