> This has certainly appened, *but* I have only see it happen with
> downloads
> of Sarge images as amd64 are not mentioned on the sarge pages (because it
> was not a release arch). To the best of my recollection, I have never yet
> seen this happen with Etch images.
me neither but from the po
afaict you currently use symlinks to point at the current version of
daily/weekly builds. This means that users who resume a download after a new
release will most likely get a mixed (and therefore broken) image.
changing that to a http redirect would mean that users would get a directory
listi
> > afaict you currently use symlinks to point at the current version of
> > daily/weekly builds. This means that users who resume a
> download after a
> > new release will most likely get a mixed (and therefore broken) image.
> >
> > changing that to a http redirect would mean that users would
It has been stated that the multi arch cd contains source for all packages
it contains but does it contain the build dependencies for those packages?
and if not why not?
After all source code isn't much use (and probablly doesn't meet the gpl
definition of source code) if the stuff needed to build
http://cdimage.debian.org/ redirects me to a page on www.debian.org which links
back to http://cdimage.debian.org/debian-cd which only contains etch images.
this makes it rather hard to find the sarge images. I eventually managed it by
using ftp rather than http and hence getting a top level dir
Then there was the short netbook boom, but AFAIR some early ones
had 64bit CPUs but 32bit-only firmware.
My memory is that at the height of the boom the dominant processors
were the N270 and N280, which are 32-bit only. By the time 64-bit
netbook processors showed up the boom was on the dec
The i386/amd64/powerpc DVD is more problematic as having all desktops will
completely fill the DVD leaving no room for other packages with a high
popcon score.
Proposal is therefore to drop powerpc support from this DVD. With only
i386 and amd64 there is still room for the top ~2600 packages o
The initial announcement of the mulit-arch DVD [1] said
"
There is also a combined amd64/i386/powerpc/source DVD which should
contain most of what people will commonly want to install on each of
those 3 arches, roughly equivalent to the contents of the first 3-4
CDs or so each. Binary-all package
"The source code for a work means the preferred form of the work for
making modifications to it. For an executable work, complete source
code means all the source code for all modules it contains, plus any
associated interface definition files, plus the scripts used to
control compilat
I am working on building CDs images for raspbian (a derivative.
I would like to change the name of the debian directory on the CDs to
make it less confusing for users. That leaves me with two questions.
1: will this cause problems for apt?
2: assuming it doesn't cause problems for apt how do I
Package: debian-cd
Severity: wishlist
when I look at the jigdo files i've generated I see
"ShortInfo='Debian GNU/Linux 7.0 "Wheezy" - Official Snapshot
armhf CD Binary-1 20121203-21:36 (20121203)'"
any idea how to change that to say raspbian?
ok I found the answer, it's hardcoded, not in an
Package: debian-cd
I've been working on trying to build cd images for raspbian using
debian-cd. While doing this I found that when building source cds
which_deb only looks for i386 and amd64 packages files. If it finds
neither it fails horriblly. This prevents building source CDs for
derivati
12 matches
Mail list logo
