The debian-private mailing list leak, part 1. Volunteers have complained about Blackmail. Lynchings. Character assassination. Defamation. Cyberbullying. Volunteers who gave many years of their lives are picked out at random for cruel social experiments. The former DPL's girlfriend Molly de Blanc is given volunteers to experiment on for her crazy talks. These volunteers never consented to be used like lab rats. We don't either. debian-private can no longer be a safe space for the cabal. Let these monsters have nowhere to hide. Volunteers are not disposable. We stand with the victims.
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: dchanges, architecture component, parseable filenames

Bruce Perens writes:
>
>> to move to python for the next major version.
>> I tried perl for my latest version of dpkg-ftp and didn't like it.
>
>I am very tempted to re-write Perl scripts in Python whenever I have to
>work on them. It's annoying to have to add _yet_another_language_, but
>Perl grosses me out sometimes.
>
>The Python distribution isn't larger than perl, is it? Perl 5 carries
>all of the same extra baggage as Python.

binary packages are perl 1.7M, python 1.9M, however you must have tk,
tcl, xlib installed (this is going to be fixed).

>> I am also happy to help implement the
>> ftpsite side of things as well (again in python).
>
>Go for it! Nobody else has volunteered and I was afraid I'd have to
>do it.

I am currently working on a package of modules for doing various
sub-tasks and will put it all together (it is someways off).  However
I am a bit net limited so will need someone to help with testing
(someone who has a mirror).

><deleted good reasons for not mailing in .changes files> 

Ok, forget that idea.

>> After the files have been installed an announcement can then be sent
>> to the required mailing lists.
>
>I think a bit of automatic reformatting to make the parse-able .changes
>file format into something easier for people to read would be
>appropriate when mailing the announcement.

Currently people often post changes that look like

<some general comments>

<then the changes file information>

We should incorpate this some how? (Extra field Message: perhaps)

>> IMO an automated system shouldn't allow people to place packages in
>> base/high proirity/mark essential without checking with Carl in some
>> way (the programs that is).
>
>Yes, but they should specify the section and priority in the .changes
>file so that the archive maintainer only has to approve it when the first
>upload happens or when a section/priority is changed. Let's not make the
>archive maintainer have to guess this stuff on his own.

I should probably add a further item to the Files field:

<md5sum> <size> <section> <priority> <filename>

when I release a new major version.

Andy.