On Tue, March 15, 2011 21:40, Joerg Jaspert wrote:
The new implementation is currently only used for suites that are not
marked as untouchable. Oldstable and stable will switch during the next
point release.
Have you (or anyone else) verified that any tools in {old,}stable
parsing contents
On Sat, Mar 12, 2011 at 11:10 PM, Kurt Roeckx k...@roeckx.be wrote:
I mean, I really don't understand why you can't atleast list the
other files from the package.
I've added a de-duplication mechanism.
Torsten
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject
On Sat, 2011-03-12 at 11:01 +0100, Torsten Werner wrote:
we have disabled the contents generator of apt-ftparchive and replaced
it by a new implementation in dak. There are some visible changes:
[...]
The new implementation is currently only used for suites that are not
marked as untouchable.
The new implementation is currently only used for suites that are not
marked as untouchable. Oldstable and stable will switch during the next
point release.
Have you (or anyone else) verified that any tools in {old,}stable
parsing contents files are compatible with the new structure (and
Hi,
we have disabled the contents generator of apt-ftparchive and replaced
it by a new implementation in dak. There are some visible changes:
1) Contents-udeb.gz and Contents-udeb-nf.gz are now available under
their canonical names main/Contents-amd64.gz and non-free/Contents-amd64.gz.
2) The
Hi,
On Samstag, 12. März 2011, Torsten Werner wrote:
The new implementation is currently only used for suites that are not
marked as untouchable. Oldstable and stable will switch during the next
point release.
Why switch stable and oldstable at all?
cheers,
Holger
signature.asc
On Sat, Mar 12, 2011 at 11:01:21AM +0100, Torsten Werner wrote:
we have disabled the contents generator of apt-ftparchive and replaced
it by a new implementation in dak. There are some visible changes:
[Contents.gz]
2) The encoding in proper UTF-8. ISO8859-1 filenames are re-coded
On Sat, Mar 12, 2011 at 11:25 AM, Holger Levsen hol...@layer-acht.org wrote:
Why switch stable and oldstable at all?
Why not? Should we maintain two different configurations for several
years for no obvious reason?
Torsten
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
On Sat, Mar 12, 2011 at 11:25:32 +0100, Holger Levsen wrote:
Hi,
On Samstag, 12. März 2011, Torsten Werner wrote:
The new implementation is currently only used for suites that are not
marked as untouchable. Oldstable and stable will switch during the next
point release.
Why switch
Hi Torsten,
On Samstag, 12. März 2011, Torsten Werner wrote:
Why switch stable and oldstable at all?
Why not? Should we maintain two different configurations for several
years for no obvious reason?
well, the obvious reason is to not break Debian stable (and oldstable), like
it happened
On Sat, Mar 12, 2011 at 11:01:21AM +0100, Torsten Werner wrote:
5) Packages with duplicate filenames are marked just as such and no
contents is recorded, e.g.
DUPLICATE_FILENAMES text/inorwegian,text/wnorwegian
So basicly apt-file search will fail to find any file in
inorwegian and
* Torsten Werner twer...@debian.org, 2011-03-12, 11:01:
2) The encoding in proper UTF-8. ISO8859-1 filenames are re-coded
automatically. To find out what happens to other encodings is left as an
exercise to the reader. :)
What's the point of messing with encodings?
5) Packages with duplicate
]] Jakub Wilk
| * Torsten Werner twer...@debian.org, 2011-03-12, 11:01:
| 2) The encoding in proper UTF-8. ISO8859-1 filenames are re-coded
| automatically. To find out what happens to other encodings is left as an
| exercise to the reader. :)
|
| What's the point of messing with encodings?
On 2011-03-12, Tollef Fog Heen tfh...@err.no wrote:
]] Jakub Wilk
| * Torsten Werner twer...@debian.org, 2011-03-12, 11:01:
| 2) The encoding in proper UTF-8. ISO8859-1 filenames are re-coded
| automatically. To find out what happens to other encodings is left as an
| exercise to the reader. :)
On Sat, Mar 12, 2011 at 03:30:03PM +0100, Tollef Fog Heen wrote:
]] Jakub Wilk
| Shouldn't dak reject debs with duplicate filenames in the first place?
No, packages might very well ship duplicate files (think all mtas
shipping /usr/sbin/sendmail) but they then have to conflict + replace.
On Sat, Mar 12, 2011 at 2:02 PM, Kurt Roeckx k...@roeckx.be wrote:
So basicly apt-file search will fail to find any file in
inorwegian and wnorwegian?
It won't find any files currently for both packages.
Why? What's wrong with the old way of doing it?
Both packages ship symlinks with the
On Sat, Mar 12, 2011 at 07:53:34PM +0100, Torsten Werner wrote:
On Sat, Mar 12, 2011 at 2:02 PM, Kurt Roeckx k...@roeckx.be wrote:
So basicly apt-file search will fail to find any file in
inorwegian and wnorwegian?
It won't find any files currently for both packages.
$ apt-file search
On Sat, Mar 12, 2011 at 8:28 PM, Kurt Roeckx k...@roeckx.be wrote:
$ apt-file search bokmaal.aff
inorwegian: /usr/lib/ispell/bokmaal.aff
$ apt-file search bokmål.aff
inorwegian: /usr/lib/ispell/bokmål.aff
$ zgrep inorwegian Contents-amd64.gz
DUPLICATE_FILENAMES
text/inorwegian,text/wnorwegian
On Sat, Mar 12, 2011 at 09:44:51PM +0100, Torsten Werner wrote:
On Sat, Mar 12, 2011 at 8:28 PM, Kurt Roeckx k...@roeckx.be wrote:
$ apt-file search bokmaal.aff
inorwegian: /usr/lib/ispell/bokmaal.aff
$ apt-file search bokmål.aff
inorwegian: /usr/lib/ispell/bokmål.aff
$ zgrep
On Sat, Mar 12, 2011 at 11:06:41PM +0100, Kurt Roeckx wrote:
On Sat, Mar 12, 2011 at 09:44:51PM +0100, Torsten Werner wrote:
On Sat, Mar 12, 2011 at 8:28 PM, Kurt Roeckx k...@roeckx.be wrote:
$ apt-file search bokmaal.aff
inorwegian: /usr/lib/ispell/bokmaal.aff
$ apt-file search
20 matches
Mail list logo
