Re: New package doesn't fix the problem in the old version

[Raf Czlonka]

Hi Ian,

Thanks for taking the time to reply.

> > > All I was trying to do was to establish was whether you're being
> > > lazy/unhelpful or is there a policy which I've missed as, [...]

I admit that I should have allowed a third possibility here.

> There is a third possibility which is that the maintainer has made a
> judgement that this bug is not worth going to special effort to fix in
> the package.  Policy does not need to be involved.

My point is exactly that: "who makes the call?".
It's not just about that package and that particular bug.
Maybe there should be a clear policy, which should apply to all releases
which are fully fledged (stable, testing, unstable[0]), on what is
deemed to be called a bug fix - IMHO uninstall (purge rather) a package
and install it again is not.
Where should individual judgement end and a clear policy/good
practice/standard way of doing things, start?
If we scale it (might be a bit far-fetched, but it really isn't IMHO)
we get to the point where personal judgement and opinion takes
precedence over everything else and is quite harmful[1].

> The suggestion that someone is or might be "lazy/unhelpful" is not
> appropriate.

It should have read: "lazy or unhelpful or ..." but because of there
being two "ORs" I shortened it. As mentioned above I think I should have
included a possibility of a third one. This however doesn't change the
fact that "lazy" or "unhelpful" are some of many human states of mind,
and therefore I don't see it as inappropriate to enumerate them as one
is perfectly entitled to them. Besides, I gave it only as an option and
yes, should have included more to choose from.
I didn't mean any harm by it.

[0] experimental excluded for obvious reasons
[1] http://blog.aurel32.net/?p=47 - while the blog post itself is
valuable, the links included in there show exactly what I have in mind

Ta,
-- 
Raf


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20111008060729.GA7757@thor.local

Re: python 2.7 in wheezy

[peter green]

Ummm ... don't we strongly encourage all package maintainers to read
d-d-a?  If not, we should.  It is very low traffic and sometimes
important.



Sure: “All developers are expected to be subscribed to this list.” [0],
but Oliver was referring to “users”. On the other hand, his example mail
(To: duplic...@packages.debian.org) is obviously sent to developers, so
I'd guess no harm is done for our users.
Remember the removal mails also end up in the history on packages.qa.debian.org 
which afaict is the main point of reference for those who are trying to find 
out what is going on with a package.


Not everyone who has an interest in why the package they rely on is suddenly
no longer in testing is a dd or a package maintainer.



--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4e8f9a4f.80...@p10link.net

Re: Unix Time Zone Format

[Russ Allbery]

Ben Finney  writes:

> That will be good, but we still need to make a lot of noise about this.
> It's ludicrous that any idiot with a lawyer can bring down a resource
> like the site hosting Olsen timezone data, even temporarily.

ado took the site down voluntarily (almost certainly), so there's really
nothing to protest other than the concept of damages for ongoing
infringment after notification, about which making a lot of noise will do
precisely zero.  It looks like the tz database was an innocent bystander
in a legal fight between two other companies and the whole thing will blow
over once that's sorted out and the actual nature of the tz database was
established.

All you're going to accomplish at this point by making a lot of noise is
to make life even more difficult for ado, so please don't.  Please
remember that he was using a server at his job for this (a US government
server, no less), so he's going to be maximally careful about not turning
this into a problem for his employers.

Once all the details are out and the case is either resolved or there's
some clear idea how we can help is the time to make noise if it's
appropriate then.  Right now, lawyers from the IETF are already involved
and the EFF has already been notified, and those of us who are
well-meaning but don't know how to properly handle the specific legal
situation should really just be quiet and let the lawyers handle it.

-- 
Russ Allbery (r...@debian.org)   


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87liswwf91@windlord.stanford.edu

Re: python 2.7 in wheezy / removal messages without reason

[Joachim Wiedorn]

Ben Finney  wrote on 2011-10-08 07:34:

> Why did it take so long? Aptitude shows immediately that ‘duply’ was to
> be removed because ‘duplicity’ was to be removed; and looking one step
Usually I use Debian Stable as productive system. So aptitude would be
not a help. I looked on packages.qa.debian.org and further ... because of
the mail "duply REMOVED from testing".

> further, that ‘duplicity’ was to be removed because the available
> version has a dependency on “python (< 2.7)”.
Inside the named site http://release.debian.org/britney/hints/jcristau
in the mail I could not found this information (and also not in the mail).

> The tools available on your system can show the reason. Is there another
> question you have that I'm not getting?
No.

---
Have a nice day.

Joachim (Germany)


--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20111008002009.436ce...@jupiter.home

Re: Unofficial Debian Monthly Testing Snapshot Release (version 2011.10)

[Michael Gilbert]

Correct gpg signature this time:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi all,

I am pleased to announce the unofficial Debian monthly testing snapshot
release for October 2011 (version 2011.10).  This release is currently
available for i386 and amd64 as iso images downloadable from:

http://alioth.debian.org/~gilbert-guest/snapshots/2011.10/debian-testing-snapshot-2011.10-i386-mini.iso
sha512sum: 
01ff749fd76c84b2b60733b934d13597b85d26c80a01fec8486b56fa2d6be460378309ab8134b2ef8ea7b8eafa0f4fcfc57cb2c8997a161643ad2b350efad1a6
http://alioth.debian.org/~gilbert-guest/snapshots/2011.10/debian-testing-snapshot-2011.10-amd64-mini.iso
sha512sum: 
a118e5bceeb457f536b9232b769f07fc86c421264c7c12b14d1c99696657c5f441fec291e4926e8a219a37bb769f1f22330856c5ce8b95aa43defb15f637260a

These files can be written to CD or DVD media or directly to a USB
stick. Instructions for USB installation can be found here:
http://www.debian.org/releases/squeeze/i386/ch04s03.html.en

IMPORTANT: There will be no inherent security support for these
snapshot releases.  The images do automatically set up testing-security
as an apt source during installation, so any DTSA's (Debian Testing
Security Advisories) will be automatically applied to snapshot
installations. However, the security team does not issue many updates
this way anymore (optioning instead to primarily use unstable uploads
as a means to fix testing). This is an area that could potentially be
improved if there are volunteers interested in this problem. For more
information on current testing security processes, see:
http://svn.debian.org/wsvn/secure-testing/doc/narrative_introduction

Ideally for those wishing to have a mostly security supported system,
the snapshot media will simply be a reliable stepping stone for
installation followed by an upgrade to testing proper, which does
receive quasi-official support from the security team (i.e. uploads to
unstable that transition to testing).

To upgrade from a previous snapshot, change your existing snapshot entries
in /etc/apt/sources.list to:

deb http://snapshot.debian.org/archive/debian/20110930T160956Z testing main
deb-src http://snapshot.debian.org/archive/debian/20110930T160956Z testing main

Note that upgradability of individual packages isn't necessarily
guaranteed.

Note that this is an unofficial project since it does not come with the
backing or support from Debian as a team, but hopefully that will
change in the future as the concept is proven out.

Anyway, enjoy!

Best wishes,
Mike Gilbert
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)

iQQcBAEBCAAGBQJOj2fNAAoJELjWss0C1vRzWGgf/itcKH4NRNVenguruzev3+XW
YoWxTd1Wzli0/TYdnXDPxVWEWxnT7j1ciTC00YRiam2Kd3FX01jtn0sbsRJPsd7U
6mUYqMYQnRwxg8hJUA4ZlgjwZ+OQxKQ3RsIAJvW/5v8uig9cN4EWtPtP6fhngBHW
xkRMAMoalrPY7AQMf0PGtEHPrtM2sFW8fSWbOKP58jQQJd/WbOkdkbJ6ho+ml/wI
rqHTMnPfLAmOes3Rb66krun7ZXVtn2NaRa2/ZlIYVs38kL6HGKoFCLFsmWE2Neaa
aBQnDZSnuCNwz6a7ZVGuDW3Xm8fV7jN/aZdpOznGThKXjnnQIOVNRQwu6YeUI1k+
enSswgPdowthDRIW+wI1ojcyCnueN7BUKy4zj8yQ4pWDQnF2krlN05pGymGYhlan
txUioAqwziir+iwbHqkqwarxQBzHa6BwFDjpqVphyq3tI9qZM9HmCdEK38PFw33V
mho95fN6yXFTTVAXzECN87ee6lOlONcc243LzsCeArkNKL9RfcE+SBwuckhKZKrW
12UYciEGOR+lm01Sb5gWBNpNs5FWQaxB6UWwLfKZSo4iJUbWeEejz6GWoorLoXPS
XRznuB3b8Bwdz63cLsC5vdepv6y6eDtmKOb7I7Z+lp5tXTzFGebKWbkmsL5btuER
+PZJoLd34lIKW+6TZ2AwfXIJuHPxHv3X6vY9Y7DN6TiPbZR8HMhgJQJAxcOVicUM
c6/g1xJUopLJqOeaTyZwCPuJlW7Y2wvox1QdGYW2iRwBmZCg8TaqGjRCIbi/aQf0
QvYlKV/OjeRCRbopzW71lqlwih7SJmb062aC1epvo+gRjPaRsSR4uCRnLwsOePro
7+yyMymzAKHybSUMkxdkkybP3It967RXT6mLQAKlvNB3b8PsPIZSnRXnUAca04YJ
/G9snGIAA1A9cFUdBRsmgUQ93xMZFIHNatqc87ue8ZwG5fWC+KoYwpzfp514Y4+4
bJGYFKE+HU4emGogrbRFooCHguaNdzllEZla5GtoARqm+2mLMGbBS+aPBDcNQAQ4
2SCgxQ5bmcnB7Zh+vgR9/qPKVI/O23kZn8Csq/5FRlDiWxxa9yCjfWFG9YRFDbZv
5jhw5wfpMcCKcz0B5B+Soh+qeedVjcnnka1a40ssyFLSBxhaVyrFvBnQocLSwmLg
OpbAreBMBL0doHS/pQwMH/Y7Cjs+x5ZoWq8Xe4wnrqUe9VQS0v+g0yMsAVh5ILxP
psZDysTtip1gam+pFVKD2q+rj3vfmX0zrk/X6pv2XJlPd3NFGbiTnpfSj1uL7+uN
L03EzWHAEeuggGUfLy+3jOtVqr6onl00ddl/XW1k/E74E1BjEgmSXKMYBAG7M70=
=nuw8
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20111007165859.95f776249e10255ae52e1...@gmail.com

Re: python 2.7 in wheezy / removal messages without reason

[Ben Finney]

Joachim Wiedorn  writes:

> But nevertheless I had to analyse the removing of my package (duply).
> After a while

Why did it take so long? Aptitude shows immediately that ‘duply’ was to
be removed because ‘duplicity’ was to be removed; and looking one step
further, that ‘duplicity’ was to be removed because the available
version has a dependency on “python (< 2.7)”.

> I saw the reason was duplicity - but why? Until now I don't know the
> deeper reason - and I haven't found the reason on debian-devel.

The tools available on your system can show the reason. Is there another
question you have that I'm not getting?

-- 
 \   “As far as the laws of mathematics refer to reality, they are |
  `\not certain, and as far as they are certain, they do not refer |
_o__)  to reality.” —Albert Einstein, 1983 |
Ben Finney


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87k48gzgjy@benfinney.id.au

Re: Unix Time Zone Format

[Ben Finney]

Russ Allbery  writes:

> Weaver  writes:
>
> > This Intellectual property rubbish is beginning to make me angry.  What
> > now?  Are we expected, each and everyone of us, supposed to pay a
> > stipend to some johnny-come-lately opportunist?
>
> > http://blog.joda.org/2011/10/today-time-zone-database-was-closed.html
>
> It's already back up and running at another site and a new release is
> being planned.  I suspect the lawsuit will blow over in short order.

That will be good, but we still need to make a lot of noise about this.
It's ludicrous that any idiot with a lawyer can bring down a resource
like the site hosting Olsen timezone data, even temporarily.

-- 
 \“All persons, living and dead, are purely coincidental.” |
  `\   —_Timequake_, Kurt Vonnegut |
_o__)  |
Ben Finney


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87obxszgtx@benfinney.id.au

Re: New package doesn't fix the problem in the old version

[Ian Jackson]

Julien Cristau writes ("Re: New package doesn't fix the problem in the old 
version"):
> On Fri, Oct  7, 2011 at 18:40:10 +0100, Raf Czlonka wrote:
> > On Fri, Oct 07, 2011 at 06:09:18PM BST, Daniel Baumann wrote:
> > >   * this is a colossal waste of time.
> > 
> > All I was trying to do was to establish was whether you're being
> > lazy/unhelpful or is there a policy which I've missed as, [...]

There is a third possibility which is that the maintainer has made a
judgement that this bug is not worth going to special effort to fix in
the package.  Policy does not need to be involved.

The suggestion that someone is or might be "lazy/unhelpful" is not
appropriate.

> Looks like it's the former.

The suggestion that someone is or might be "lazy/unhelpful" is not
appropriate.

Ian.


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20111.23271.215195.156...@chiark.greenend.org.uk

Unofficial Debian Monthly Testing Snapshot Release (version 2011.10)

[Michael Gilbert]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi all,

I am pleased to announce the unofficial Debian monthly testing snapshot
release for October 2011 (version 2011.10).  This release is currently
available for i386 and amd64 as iso images downloadable from:

http://alioth.debian.org/~gilbert-guest/snapshots/2011.10/debian-testing-snapshot-2011.10-i386-mini.iso
sha512sum:
01ff749fd76c84b2b60733b934d13597b85d26c80a01fec8486b56fa2d6be460378309ab8134b2ef8ea7b8eafa0f4fcfc57cb2c8997a161643ad2b350efad1a6
http://alioth.debian.org/~gilbert-guest/snapshots/2011.10/debian-testing-snapshot-2011.10-amd64-mini.iso
sha512sum:
a118e5bceeb457f536b9232b769f07fc86c421264c7c12b14d1c99696657c5f441fec291e4926e8a219a37bb769f1f22330856c5ce8b95aa43defb15f637260a

These files can be written to CD or DVD media or directly to a USB
stick. Instructions for USB installation can be found here:
http://www.debian.org/releases/squeeze/i386/ch04s03.html.en

IMPORTANT: There will be no inherent security support for these
snapshot releases.  The images do automatically set up testing-security
as an apt source during installation, so any DTSA's (Debian Testing
Security Advisories) will be automatically applied to snapshot
installations. However, the security team does not issue many updates
this way anymore (optioning instead to primarily use unstable uploads
as a means to fix testing). This is an area that could potentially be
improved if there are volunteers interested in this problem. For more
information on current testing security processes, see:
http://svn.debian.org/wsvn/secure-testing/doc/narrative_introduction

Ideally for those wishing to have a mostly security supported system,
the snapshot media will simply be a reliable stepping stone for
installation followed by an upgrade to testing proper, which does
receive quasi-official support from the security team (i.e. uploads to
unstable that transition to testing).

To upgrade from a previous snapshot, change your existing snapshot
entries in /etc/apt/sources.list to:

deb http://snapshot.debian.org/archive/debian/20110930T160956Z testing
main deb-src http://snapshot.debian.org/archive/debian/20110930T160956Z
testing main

Note that upgradability of individual packages isn't necessarily
guaranteed.

Note that this is an unofficial project since it does not come with the
backing or support from Debian as a team, but hopefully that will
change in the future as the concept is proven out.

Anyway, enjoy!

Best wishes,
Mike Gilbert
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)

iQQcBAEBCAAGBQJOj1+2AAoJELjWss0C1vRzjokgAJdR1nWGde/EyQA83Y8ZLbCL
A+lt3T8NCjTiMf3N0zR35guGrzPDo23IbIUAz8lyRhmE2zDHkOeHSsf6r7p1mcJ8
s9IPncBd6ekgM7GYk1tTfHAjoobbkFEkBkNCYbM1UYvfQ1QHWl0lA159jnSj+Em1
HOvPDgN6i0IuRyvmzeDdSjBPhqM24zfp6CiVsNqyAMR24jQil3CV7FKlID0IM8Wf
uQzVcMVSqlda1Yq4ESlw+s/USo41z9M2+MPEwtFyPMmpgNb6Rt7JQSAFRKS3jvTG
7XCx8Nvxvw6n0ImnSG58Hj1032F3CfufgRZXOjIzJgBmgfLUxn31FfmwQd+iaPRw
nVjLoq/p9FqO5TNG16yMaf16nEPK/WbsG6DZEuTcrkr/l9J9eOCKQpVfnALVEOsG
DagcjnrgIdCkDWI7a1ld9kbny1Fseov12ZHArnl3QutFIMi6vA9iNl3FA6aD39je
n3av0hjDAdwqG0Jp1rfX5GioplogFs4PDTkWs8V7qgoDaKQvol84lmTBl48zCndv
TWeMkbfWx/AyGRrXf2bJovNuGnG6lW9Y4FND+u6LrZ5TbYRnNvcWWtqLfgkRodDG
1gh+UZLL2iRkELapJ9307O/qSOq9ZSRbYdyi1qcS9pPbdIVPSvU3Reh3ZqKY0+Xj
4iNbTlVmx6S8bWUV48JSLGJHDInlPHtAe0WqXP7GNXS0oZas/NBGrYce/Rbw9ebg
Nw61T///RN2tkb9OVRrT79q5JL6jPbY9XNCfobNJihw9f4VswtzpR99uuCT8YWC2
QQtlw7cw+Kkz13SgB5qRTfgan5FmDQk3yT1k8UIIF2xptqRUXfFB7ICzpPR3TZVX
3KIlCd33XJytNbHPm8APk38O93+qQDQlitcwRBXEDQW9NXUNOkcBsVTVpMmsZz2V
9qoj0kDDXzUuZSO9yxBhljyjBMr7sK1HftJNe+HAczk5l4DZ80pNf/vV94B82pzS
aIDC0AR8C+XJzlO3DMdO5+Ts166z0JsAWYY6DgiYCs0EIpCz7vs9+V87qVlqcxKy
C8oVdKKlvXmgEKwav+JQS2QFLYi3nDEa1upjlEahB9dOQNtNg4Stnczad+vkb1HN
tdNJzjMg0feipGwTzFLD8rQ95ytAzEmn44i69jLo/8HkOhSYKXi+aeAeIxsZ1c4E
aBt1ZuX/3iBgx9MqP4DEoMhX2Wl7qYjJGP4DY1qr+j/mvr1kCST/CKJ9kKXtJrDL
Z8kXDvmrE5GWAQzV9JEJeeuIVrAufJtwGITE+IJDmZNmoxMl/aEcnq4viCT4TrBC
myuggdqnWcvlV6efDxveJJ0Ie16/qbUC7vHtL7im1Oc8RAoEeJIFSkE9tBI/djc=
=MftZ
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20111007162439.ffc8deb69f6e3a76e290d...@gmail.com

Bug#644654: ITP: eclipse-cdt-pkg-config -- pkg-config support for Eclipse CDT

[Jakub Adam]

Package: wnpp
Severity: wishlist
X-Debbugs-CC: debian-devel@lists.debian.org

--- Please fill out the fields below. ---

   Package name: eclipse-cdt-pkg-config
Version: 0.5.2+svn195
Upstream Author: Petri Tuononen 
URL: http://code.google.com/p/pkg-config-support-for-eclipse-cdt/
License: EPL-1.0
Description: pkg-config support for Eclipse CDT

The aim of the Eclipse plug-in is to provide automation of configuration needed
for projects using pkg-config, such as GTK+ and gtkmm.

The plug-in will set options and switches automatically that gcc needs to add
in the selected packages - specifically the header file paths, the libraries,
and some other gcc switches.



--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4e8f5713.3080...@ktknet.cz

Re: New package doesn't fix the problem in the old version

[Julien Cristau]

On Fri, Oct  7, 2011 at 18:40:10 +0100, Raf Czlonka wrote:

> On Fri, Oct 07, 2011 at 06:09:18PM BST, Daniel Baumann wrote:
> > my opinion..
> [cut]
> >   * unstable and *testing* users are supposed to be able to cope with
> > the one or other glitch, if they don't, they use stable.
> 
> I know that, thank you. I've been doing that for nearly a decade.
> 
> >   * this is a colossal waste of time.
> 
> That might be true.
> All I was trying to do was to establish was whether you're being
> lazy/unhelpful or is there a policy which I've missed as, per my earlier
> email, I can't remember last time I filed a bug which later version
> hadn't corrected, no matter how trivial it was.
> 
Looks like it's the former.

Cheers,
Julien


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20111007180017.gw2...@radis.liafa.jussieu.fr

Re: New package doesn't fix the problem in the old version

[Raf Czlonka]

On Fri, Oct 07, 2011 at 06:09:18PM BST, Daniel Baumann wrote:
> my opinion..
[cut]
>   * unstable and *testing* users are supposed to be able to cope with
> the one or other glitch, if they don't, they use stable.

I know that, thank you. I've been doing that for nearly a decade.

>   * this is a colossal waste of time.

That might be true.
All I was trying to do was to establish was whether you're being
lazy/unhelpful or is there a policy which I've missed as, per my earlier
email, I can't remember last time I filed a bug which later version
hadn't corrected, no matter how trivial it was.

Cheers,
-- 
Raf


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20111007174009.GA2944@thor.local

Re: Greaat disappointment

[Yaroslav Halchenko]

no problem Christian -- apologies accepted ;)
thanks for chiming in on the topic.

On Sat, 01 Oct 2011, Christian Brenner wrote:

> Hello Mr. Halchenko,

> I have to apologize to you for my last mail. It seems my mind was
> wandering somewhere else. As Mr. Biebl, was pointing out, you only
> responded to the initial mail.

> Sorry again,
> Christian
-- 
=--=
Keep in touch www.onerussian.com
Yaroslav Halchenko www.ohloh.net/accounts/yarikoptic


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20111007173348.ga10...@onerussian.com

Re: New package doesn't fix the problem in the old version

[Raf Czlonka]

On Fri, Oct 07, 2011 at 05:26:03PM BST, Bernhard R. Link wrote:
> As I had problems of understanding this first let me recap the
> situation:
> 
> git-stuff before 5-1 created a buggy file when getting installed that
> is still causing problems when git-stuff 7-1 is installed.
> 
> So it's not so much a bug in 7-1 but 7-1 not tidy up the mess left by
> earlier versions.

That's correct.

> As git-stuff was never released, those earlier buggy versions were
> not released either, so only people installing unstable or testing
> are effected.
>
> For not too serious stuff in unstable it is usually widely accepted
> that people sometimes might have to clean things up themselves.
> (Any cleaning code means the package is bigger for everyone and
> any fix could go wrong and introduce new bugs).

I've been using unstable exclusively for nearly 10 years.
Most if not all packages I reported bugs for DO fix the issues caused
by earlier versions, otherwise no one would use unstable if expected to
fix everything by hand.
I don't mind packages being broken, that's the reason why I use sid - to
help develop Debian, find and report bugs, etc.

> I'm not sure what the consensus for packages that were in testing
> is (or if there was a consensus at all). I guess it mostly depends
> on the time it was in testing and how complicated the fix is.
> 
> The bug was only in testing for either for 50 days or for 25 days,
> so it might depend how complex the fix is.

It shouldn't matter that it's been in testing for so long, the bug's in
unstable, and should be fixed there, even if doesn't reach testing in a
long time.
Both the bug and a fix are trivial - it's simply an entry in a cron job
file - the links I've attached have all the relevant information.

Regards,
-- 
Raf


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20111007172312.GA28774@thor.local

Re: New package doesn't fix the problem in the old version

[Daniel Baumann]

the facts..

  * #640016 was introduced in version 2-1 on 2011-08-02.

  * #640016 was reported on 2011-09-01 and fixed on 2011-09-01 in
version 5-1.

  * version 4-1 with the bug migrated on 2011-08-23 to testing,
version 7-1 without the bug migrated on 2011-09-17 to testing.

  * testing was affected by the bug for 25 days.

  * the bug is by default not in the wild (git-repositories-repack
cronjob, priority low debconf question, defaults to no).

  * the bug is just that the wrongly called scripts fails by doing
nothing. worst case: user is annoyed by an error message that
nothing happened.

  * git-stuff was not yet part of a stable release.

my opinion..

  * everything that Bernhard already said.

  * adding preinst scripts that check for certain md5sums for files
sucks, in particular since in theory, you can only get rid of them
after stable+1. so not worth the hassle, in particulary not to
blow up the package considerably and unecessarily for everyone until
stable+1, just to mitigate a minor annoyance for a handful of
people.

  * unstable and *testing* users are supposed to be able to cope with
the one or other glitch, if they don't, they use stable.

  * this is a colossal waste of time.

Regards,
Daniel

--
Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern
Email:  daniel.baum...@progress-technologies.net
Internet:   http://people.progress-technologies.net/~daniel.baumann/


--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4e8f323e.3030...@progress-technologies.net

Re: New package doesn't fix the problem in the old version

[Bernhard R. Link]

* Raf Czlonka  [111007 17:17]:
> While the new package indeed does not contain the bug itself when
> installed as a new package on a system which hadn't had it before,
> it does not fix the bug if installed on a system with the older version.

As I had problems of understanding this first let me recap the
situation:

git-stuff before 5-1 created a buggy file when getting installed that
is still causing problems when git-stuff 7-1 is installed.

So it's not so much a bug in 7-1 but 7-1 not tidy up the mess left by
earlier versions.

As git-stuff was never released, those earlier buggy versions were
not released either, so only people installing unstable or testing
are effected.

For not too serious stuff in unstable it is usually widely accepted
that people sometimes might have to clean things up themselves.
(Any cleaning code means the package is bigger for everyone and
any fix could go wrong and introduce new bugs).

I'm not sure what the consensus for packages that were in testing
is (or if there was a consensus at all). I guess it mostly depends
on the time it was in testing and how complicated the fix is.

The bug was only in testing for either for 50 days or for 25 days,
so it might depend how complex the fix is.

Bernhard R. Link


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20111007162603.gc4...@server.brlink.eu

Re: debian/rules binary and build target dependencies clarification

[Bernhard R. Link]

* Дмитрий Матросов  [111007 16:27]:
> But in the section 7.7 of Debian policy manual:
> > clean, build-arch, and binary-arch
> >Only the Build-Depends and Build-Conflicts fields must be satisfied when
> >these targets are invoked.
> > build, build-indep, binary, and binary-indep
> >The Build-Depends, Build-Conflicts, Build-Depends-Indep, and
> >Build-Conflicts-Indep fields must be satisfied when these targets are
> >invoked.
>
> And footnote 55:
> > Anyone building the build-indep and binary-indep targets is assumed to be
> > building the whole package, and therefore installation of all build
> > dependencies is required.
>
> So, as i understand, in this case dependencies will look like
>
>binary : binary-arch  binary-indep
>binary-indep : build-indep build-arch   

Re: python 2.7 in wheezy / removal messages without reason

[Joachim Wiedorn]

David Prévot  wrote on 2011-10-06 21:26:

> Sure: “All developers are expected to be subscribed to this list.” [0],
> but Oliver was referring to “users”. On the other hand, his example mail
> (To: duplic...@packages.debian.org) is obviously sent to developers, so
> I'd guess no harm is done for our users.

It would be very helpful to be subscribed to debian-devel - and I am
subscribed.

But nevertheless I had to analyse the removing of my package (duply).
After a while I saw the reason was duplicity - but why? Until now I don't
know the deeper reason - and I haven't found the reason on debian-devel.
So I can only wildcatting.

---
Have a nice day.

Joachim (Germany)


--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20111007172801.1cf03...@jupiter.home

Re: Unix Time Zone Format

[Russ Allbery]

Weaver  writes:

> This Intellectual property rubbish is beginning to make me angry.  What
> now?  Are we expected, each and everyone of us, supposed to pay a
> stipend to some johnny-come-lately opportunist?

> http://blog.joda.org/2011/10/today-time-zone-database-was-closed.html

It's already back up and running at another site and a new release is
being planned.  I suspect the lawsuit will blow over in short order.  It's
obviously groundless and there are tons of expert witnesses who can
testify to that, but ado is a conservative sort of guy and will be
careful.

-- 
Russ Allbery (r...@debian.org)   


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/8762k03jni@windlord.stanford.edu

New package doesn't fix the problem in the old version

[Raf Czlonka]

Hi all,

Recently I filed a bug report against git-stuff[0] which itself been
closed with the explanation that it's a duplicate of an earlier bug[1]
which itself has been closed by the maintainer claiming it had been
fixed in version 5-1.

While the new package indeed does not contain the bug itself when
installed as a new package on a system which hadn't had it before,
it does not fix the bug if installed on a system with the older version.

As you can read in the first link, maintainer's not interested in 
including the fix for older versions.

Widely available link[2] reads:

Debian bug reports should be closed when the problem is fixed. Problems in
packages can only be considered fixed once a package that includes the
bug fix enters the Debian archive.

The way I read it is: "the new version has to introduce the fix for
older ones". You shouldn't need to remove older version and installing
the new one after or even editing any files yourself if the new version
allegedly fixes the issue.

Since the new version doesn't override the file in question it cannot
possibly treated as a fix.

Unless I'm missing something?

[0] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644017
[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640016
[2] http://www.debian.org/Bugs/Developer#closing

Regards,
-- 
Raf


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20111007151708.GA28182@thor.local

debian/rules binary and build target dependencies clarification

[Дмитрий Матросов]

Hello.

Not sure this is correct maillist, though. I can't clearly understand
dependencies between debian/rules binary and build targets.

Let's assume, that both 'build-arch' and 'build-indep' targets provided.

In the Debian policy manual section 4.9 written:

> The build target should depend on those of the targets build-arch and
> build-indep that are provided in the rules file.
> ..
> binary may be (and commonly is) a target with no commands which simply
> depends on binary-arch and binary-indep.
> ..
> Both binary-* targets should depend on the build target, or on the
> appropriate build-arch or build-indep target, if provided,..

So, as i understand, this will look like

   binary : binary-arch  binary-indep
   binary-arch : build-arch
   binary-indep : build-indep
   build : build-arch  build-indep

But in the section 7.7 of Debian policy manual:
> clean, build-arch, and binary-arch
>Only the Build-Depends and Build-Conflicts fields must be satisfied when
>these targets are invoked.
> build, build-indep, binary, and binary-indep
>The Build-Depends, Build-Conflicts, Build-Depends-Indep, and
>Build-Conflicts-Indep fields must be satisfied when these targets are
>invoked.

And footnote 55:
> Anyone building the build-indep and binary-indep targets is assumed to be
> building the whole package, and therefore installation of all build
> dependencies is required.

So, as i understand, in this case dependencies will look like

   binary : binary-arch  binary-indep
   binary-indep : build-indep build-arch   

Bug#644622: ITP: libmojo-server-fastcgi-perl -- Mojolicious FastCGI Server

[gregor herrmann]

Package: wnpp
Owner: gregor herrmann 
Severity: wishlist
X-Debbugs-CC: debian-devel@lists.debian.org,debian-p...@lists.debian.org

* Package name: libmojo-server-fastcgi-perl
  Version : 0.1
  Upstream Author : Árpád Szász 
* URL : http://search.cpan.org/dist/Mojo-Server-FastCGI/
* License : Artistic-2.0
  Programming Lang: Perl
  Description : Mojolicious FastCGI Server

Mojo::Server::FastCGI is a portable pure-Perl FastCGI implementation as
described in the FastCGI Specification.

Mojolicious::Command::fastcgi is a command interface to
Mojo::Server::FastCGI.



-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20111007131654.ga12...@belanna.comodo.priv.at

Weird removal messages sent by "britney" without enough user friendly details - Was: Re: python 2.7 in wheezy

[Olivier Berger]

Hi.

Le jeudi 06 octobre 2011 à 21:26 -0400, David Prévot a écrit :
> Le 06/10/2011 20:43, Peter Samuelson a écrit :
> > 
> > [Olivier Berger]
> >> For users, which don't read d-d-a and receive such emails (below),
> >> it's a bit unclear what's really happening, IMHO :-/
> > 
> > Ummm ... don't we strongly encourage all package maintainers to read
> > d-d-a?  If not, we should.  It is very low traffic and sometimes
> > important.
> 
> Sure: “All developers are expected to be subscribed to this list.” [0],
> but Oliver was referring to “users”. On the other hand, his example mail
> (To: duplic...@packages.debian.org) is obviously sent to developers, so
> I'd guess no harm is done for our users.
> 

I may be wrong, but (advanced) users can also be notified of such
messages when they are subscribed to packages via the PTS.

Which is good advice, IMHO, to monitor packages in Debian when your
business depends on some volunteer maintainer work: you'd like to know
in advance such facts as a package being pulled out of Debian, early
enough ;)

Maybe I'm the only one doing that though (and particularly important, as
duplicity runs my backups)

Maybe I could file a wishlist on britney somewhere ?

> 0:
> http://www.debian.org/doc/manuals/developers-reference/resources.html#core-devel-mailing-lists

Best regards,
-- 
Olivier BERGER 
http://www-public.it-sudparis.eu/~berger_o/ - OpenPGP-Id: 2048R/5819D7E8
Ingénieur Recherche - Dept INF
Institut TELECOM, SudParis (http://www.it-sudparis.eu/), Evry (France)


--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1317985373.3877.4.ca...@inf-8657.int-evry.fr

Unix Time Zone Format

[Weaver]

This Intellectual property rubbish is beginning to make me angry.
What now?
Are we expected, each and everyone of us, supposed to pay a stipend to
some johnny-come-lately opportunist?

http://blog.joda.org/2011/10/today-time-zone-database-was-closed.html

Regards,

Weaver.


-- 
"In a world without walls and fences, 
what need have we for Windows or Gates?"
-Anon.


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20111007201632.272f5302.wea...@riseup.net

Bug#644586: ITP: exodusII -- Finite element analysis storage library

[Alastair McKinstry]

Package: wnpp
Severity: wishlist
Owner: Alastair McKinstry 

* Package name: exodusII
  Version : 5.1
  Upstream Author : Gregory Sjaardema 
* URL : http://sourceforge.net/projects/exodusii/
* License : BSD
  Programming Lang: C
  Description : Finite element analysis storage library

EXODUS II is a model developed to store and retrieve transient data for finite 
element analyses.
It is used for preprocessing, postprocessing, as well as code to code data 
transfer. 
ExodusII is based on netcdf. Includes the nemesis parallel extension.



-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20111007080348.32380.81086.report...@ailm.sceal.ie

Re: Bug#644535: ITP: eclipse-autotools -- Eclipse Linux Tools: Autotools support for CDT

[Miles Bader]

Jakub Adam  writes:
> With this additional support, a vast repository of C/C++ code can be
> checked out, built, and maintained under the CDT rather easily without
> having to resort to the command line.

Nice!

[Maybe "having to resort" is a bit judgemental in tone, though ...]

-miles

-- 
Logic, n. The art of thinking and reasoning in strict accordance with the
limitations and incapacities of the human misunderstanding.


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/buowrchjmn1@dhlpc061.dev.necel.com