Hi,
On Thu, 02 Jun 2011, Ian Jackson wrote:
> If a new behaviour is needed, it should have a new name. Otherwise
> you break existing packages.
I know this. This is precisely why I'm asking the question of which
packages require this behaviour. If none or very few require it, I might
consider do
Package: general
Severity: important
Hello,
after the 2nd or 3rd wake up from hibernation, the screen is all
scrambled and I have to reboot the computer (maybe killing X would be
sufficient but in either case, my session goes down the drain).
Etienne
P.S. Thanks for making Debian!
This message has been sent to you as the final step to confirm your
email *removal* for the following list:
Texas Invitation
To confirm this unsubscription, please follow the URL below:
http://hsvpp.com/cgi-bin/dada/mail.cgi/u/txinvite/debian-devel/lists.debian.org/5BcIX2RokH8d2/
(Click the U
On Thu, Jun 2, 2011 at 6:05 PM, Robert Collins
wrote:
> On Fri, Jun 3, 2011 at 2:40 AM, Martin Owens wrote:
>> Why not just make ppa uploading simpler at the same time? (if you can
>> change the changelog file processing):
>>
>> picocom (1.4-1) debian:unstable oneiric natty maverick lucid;
>> urg
On Fri, Jun 3, 2011 at 2:40 AM, Martin Owens wrote:
> On Thu, 2011-06-02 at 13:20 +0100, Ian Jackson wrote:
>> For this to work I think the "suite" target in the changelog entry
>> should be qualified by the distro, so you could say (picking a random
>> example):
>>
>> picocom (1.4-1) debian:uns
On 3 June 2011 01:02, Cristian Henzel wrote:
> For the changelog part, I thought *not* requiring a specific suite would
> also be
> a good compromise.
Why do we even bother putting the suite into the changelog? I don't see the
point myself.
I believe it is the DISTRIBUTION header in the change
>
>
> I handle this using a set of scripts in Ubuntu's bikeshed package:
> * http://manpg.es/release-build
> * http://manpg.es/release
+1! I have been using these scripts extensively to do my releases, and
preparing the packages to upload them into the archive or
PPA's. Specifically for TestDri
Package: wnpp
Severity: wishlist
Owner: Jonas Smedegaard
* Package name: libxml-atom-microformats-perl
Version : 0.002
Upstream Author : Toby Inkster
* URL : http://search.cpan.org/dist/XML-Atom-Microformats/
* License : Artistic or GPL-1+
Programming Lang:
On Jun 02, 2011, at 10:28 AM, Peter Samuelson wrote:
>Since syncs from Debian are actually supposed to be the majority of
>packages in Ubuntu anyway, why not just do that - a real sync, not a
>fake simultaneous one. I don't live in the Ubuntu dev universe, but
>given how common of an operation th
On Thursday, June 02, 2011 02:17:14 PM Goswin von Brederlow wrote:
> Scott Kitterman writes:
> > If 3.0 (quilt) didn't apply patches by default I'd have no reason not to
> > just use it. Keeping local_options in a VCS is a bit of a workaround
> > for this, but it seems wrong to have a persistent
On Thu, Jun 2, 2011 at 8:20 AM, Ian Jackson
wrote:
...
> One thing I have done a few times is to upload the very same package
> simultaneously to (say) Debian and Ubuntu.
>
> Where the package wants to be identical, and the person doing the
> upload is the same, it would be nice if this could be m
Scott Kitterman writes:
> If 3.0 (quilt) didn't apply patches by default I'd have no reason not to just
> use it. Keeping local_options in a VCS is a bit of a workaround for this,
> but
> it seems wrong to have a persistent diff between what's in the VCS for a
> package and what's in the arc
Stefano Rivera writes:
> Hi Scott (2011.06.02_16:30:13_+0200)
>> Keeping local_options in a VCS is a bit of a workaround for this
> ...
>> I'd really like to have a way to just control this globally on my system.
>
> +1 to that. Esp for team-maintained packages where people have different
> prefe
Charles Plessy writes:
> Le Thu, Jun 02, 2011 at 11:11:30AM +0200, Goswin von Brederlow a écrit :
>>
>> apt-get source foo
>> work on package
>> debuild
>> test
>> # Optionally: Just to be nice and fill out the header
>> # This would be improved by the --record-changes discussed earlier
>> edit
Guido Günther writes:
> On Thu, Jun 02, 2011 at 11:11:30AM +0200, Goswin von Brederlow wrote:
>> Scott Kitterman writes:
>>
>> > On Wednesday, June 01, 2011 10:26:59 AM sean finney wrote:
>> >> On Wed, Jun 01, 2011 at 02:39:42PM +0200, Goswin von Brederlow wrote:
>> >> > And note that as mainta
Hello,
My name is Anna Desmond, I saw your profile today through the help of chamber
of commerce in Bamako the capital of Mali) and became interested in you, I will
also like to know you the more,and I want you to send an email to my email
address so I can give you my picture for you to know wh
On Thu, Jun 02, 2011 at 01:54:37PM +0100, Ian Jackson wrote:
> Iain Lane writes ("Re: Uploading to multiple distros"):
> > For "normal" syncs we generally advise not using syncpackage, but it
> > might make sense when doing simultaneous uploads.
>
> Hrm. So syncpackage generates a .changes for u
On Thu, Jun 02, 2011 at 01:54:37PM +0100, Ian Jackson wrote:
[...]
Hrm. So syncpackage generates a .changes for uploading to ubuntu from
the .dsc (which presumably came out of the Debian build). That does
mean though that the Ubuntu target suite is not visible in the
changelog of the ultimate U
On Thu, Jun 02, 2011 at 03:19:14PM +0200, Stefano Rivera wrote:
> Hi Ian (2011.06.02_14:54:37_+0200)
> > I wasn't aware of syncpackage. The manpage is quite discouraging.
> It's discouraging for a reason, the Ubuntu archive admins would prefer
> that we sync packages through them if possible (whi
[Ian Jackson]
> Hrm. So syncpackage generates a .changes for uploading to ubuntu from
> the .dsc (which presumably came out of the Debian build). That does
> mean though that the Ubuntu target suite is not visible in the
> changelog of the ultimate Ubuntu package. And if the package is not
> ac
I had this very same discussion with another packager and we came to the same
conclusion: changing stuff around a bit to make uploading to multiple
distributions easier, would greatly help packagers IMO.
One thing I would welcome, if possible, would be conditional build-deps, so that
you can set d
On Thu, 2011-06-02 at 13:20 +0100, Ian Jackson wrote:
> For this to work I think the "suite" target in the changelog entry
> should be qualified by the distro, so you could say (picking a random
> example):
>
> picocom (1.4-1) debian:unstable ubuntu:oneiric; urgency=low
>
> * new upstream v
Hi Scott (2011.06.02_16:30:13_+0200)
> Keeping local_options in a VCS is a bit of a workaround for this
...
> I'd really like to have a way to just control this globally on my system.
+1 to that. Esp for team-maintained packages where people have different
preferences, and QA work.
SR
--
Stefan
On Thursday, June 02, 2011 05:11:30 AM Goswin von Brederlow wrote:
> Scott Kitterman writes:
> > On Wednesday, June 01, 2011 10:26:59 AM sean finney wrote:
> >> On Wed, Jun 01, 2011 at 02:39:42PM +0200, Goswin von Brederlow wrote:
> >> > And note that as maintainer or for the VCS copy you can allw
Package: wnpp
Severity: normal
Native package written by yours truly. Pristine-tar part does not work
anymore, reason unknown. Everything is written in haXe, which entails
some problems wrt. Process control & input/output, and I have created a
branch (combined-process-input-output) in which I ha
Package: wnpp
Severity: normal
Package in good shape, reposive upstream, although getting stable
upstream sources is little tricky.
The package has pseudo build failures on kFreeBSD because of the way
disks are mounted on the buildds. I would suggest to simply exclude
kFreeBSD to avoid this hass
Package: wnpp
Severity: normal
Package in good shape, responsive (new) upstream.
--
Jens Peter Secher, GPG fingerprint 0EE5978AFE63E8A1.
A. Because it breaks the logical sequence of discussion.
Q. Why is top posting bad?
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with
Package: wnpp
Severity: normal
Package in good shape, very low upstream activity.
--
Jens Peter Secher, GPG fingerprint 0EE5978AFE63E8A1.
A. Because it breaks the logical sequence of discussion.
Q. Why is top posting bad?
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
wit
Package: wnpp
Severity: normal
Package in good shape, very low activity upstream.
--
Jens Peter Secher, GPG fingerprint 0EE5978AFE63E8A1.
A. Because it breaks the logical sequence of discussion.
Q. Why is top posting bad?
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
wit
Package: wnpp
Severity: normal
Package in good shape, upstream responsive, low activity.
--
Jens Peter Secher, GPG fingerprint 0EE5978AFE63E8A1.
A. Because it breaks the logical sequence of discussion.
Q. Why is top posting bad?
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.
Package: wnpp
Severity: normal
Package in good shape, unclear upstream development.
--
Jens Peter Secher, GPG fingerprint 0EE5978AFE63E8A1.
A. Because it breaks the logical sequence of discussion.
Q. Why is top posting bad?
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
w
Package: wnpp
Severity: normal
pam-ssh has unclear upstream development, has a lot of Debian changes,
and in general need a firm hand.
--
Jens Peter Secher, GPG fingerprint 0EE5978AFE63E8A1.
A. Because it breaks the logical sequence of discussion.
Q. Why is top posting bad?
--
To UNSUBSCRIB
On 02/06/11 23:19, Stefano Rivera wrote:
> [snip]
>> One way to enable simultaneous uploads would be to arrange for
>> dpkg-genchanges to filter out suites for "other" distros when
>> generating the .changes file. Then you would have the same files
>> being uploaded but two different .changes file
Package: wnpp
Severity: normal
Package has not been touched for years, very low activity upstream.
--
Jens Peter Secher, GPG fingerprint 0EE5978AFE63E8A1.
A. Because it breaks the logical sequence of discussion.
Q. Why is top posting bad?
--
To UNSUBSCRIBE, email to debian-devel-requ...@lis
Package: wnpp
Severity: normal
Package in good shape, upstream responsive and has a Debian guest
account for debugging failures.
--
Jens Peter Secher, GPG fingerprint 0EE5978AFE63E8A1.
A. Because it breaks the logical sequence of discussion.
Q. Why is top posting bad?
--
To UNSUBSCRIBE, ema
Hi Ian (2011.06.02_14:54:37_+0200)
> I wasn't aware of syncpackage. The manpage is quite discouraging.
It's discouraging for a reason, the Ubuntu archive admins would prefer
that we sync packages through them if possible (which results in ~1 days
wait). An API method for syncing (+ a button on la
Package: wnpp
Severity: normal
Package in good shape, very low maintenance.
--
Jens Peter Secher, GPG fingerprint 0EE5978AFE63E8A1.
A. Because it breaks the logical sequence of discussion.
Q. Why is top posting bad?
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a su
Package: wnpp
Severity: normal
Package in good shape, very low activity.
--
Jens Peter Secher, GPG fingerprint 0EE5978AFE63E8A1.
A. Because it breaks the logical sequence of discussion.
Q. Why is top posting bad?
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subje
Iain Lane writes ("Re: Uploading to multiple distros"):
> You can do this already by using syncpackage(1) from ubuntu-dev-tools ?
> I don't think the archive software looks at the changelog, but the
> distribution in the changes file.
I wasn't aware of syncpackage. The manpage is quite discoura
Package: wnpp
Severity: normal
Asunder is in good shape, upstream is responsive (and would like to not
have his email made public).
--
Jens Peter Secher, GPG fingerprint 0EE5978AFE63E8A1.
A. Because it breaks the logical sequence of discussion.
Q. Why is top posting bad?
--
To UNSUBSCRIBE, e
Bernhard R. Link writes ("Re: Behaviour of dpkg-source with "3.0 (quilt)" and
VCS and automatic patches"):
> The more Debian packages you have seen, the more different ways you
> have encountered and the less likely you are to be confused or to
> forget to apply the patches before looking at the s
Raphael Hertzog writes ("Semantic change for dpkg triggers?"):
> I am considering changing the default behaviour of dpkg triggers. [1]
> Currently when a package activates a trigger (except if it uses
> dpkg-trigger directly with the --no-await option, and that is a minority
> of cases), the triger
On Thu, Jun 02, 2011 at 01:20:08PM +0100, Ian Jackson wrote:
Didier Raboud writes ("Re: Color Management in Debian"):
Given that Debian is currently not frozen (and that the Oneiric
release will very probably happen before Wheezy's), I really think
that not uploading those packages to Debian fir
Didier Raboud writes ("Re: Color Management in Debian"):
> Given that Debian is currently not frozen (and that the Oneiric
> release will very probably happen before Wheezy's), I really think
> that not uploading those packages to Debian first would be a shame,
> as this would only mean doubling ef
Le Thu, Jun 02, 2011 at 11:11:30AM +0200, Goswin von Brederlow a écrit :
>
> apt-get source foo
> work on package
> debuild
> test
> # Optionally: Just to be nice and fill out the header
> # This would be improved by the --record-changes discussed earlier
> edit debian/patches/debian-changes-versi
Package: wnpp
Severity: wishlist
X-Debbugs-CC: debian-devel@lists.debian.org
Package name: doconce
Version: 0.5
Upstream authors: Hans Petter Langtangen
URL: http://doconce.googlecode.com/
License: BSD-3-clause
Description: document once, include anywhere
Doconce is two things:
.
1. Doconce i
On Thu, Jun 02, 2011 at 11:11:30AM +0200, Goswin von Brederlow wrote:
> Scott Kitterman writes:
>
> > On Wednesday, June 01, 2011 10:26:59 AM sean finney wrote:
> >> On Wed, Jun 01, 2011 at 02:39:42PM +0200, Goswin von Brederlow wrote:
> >> > And note that as maintainer or for the VCS copy you ca
Scott Kitterman writes:
> On Wednesday, June 01, 2011 10:26:59 AM sean finney wrote:
>> On Wed, Jun 01, 2011 at 02:39:42PM +0200, Goswin von Brederlow wrote:
>> > And note that as maintainer or for the VCS copy you can allways
>> > configure debian/soruce/local-options to unapply patches if you s
48 matches
Mail list logo
