Re: distinguish between "core" and "main"?

2011-06-04 Thread Paul Wise
On Sat, Jun 4, 2011 at 2:54 PM, Harald Dunkel wrote: > Backports for Squeeze contains just about 400 package, > AFIACS. Yep, if you want more you should either build (and upload) them yourself or talk to the maintainers of the ones you want and get them to build and upload them. Alternatively y

Re: distinguish between "core" and "main"?

2011-06-04 Thread Russ Allbery
Harald Dunkel writes: > I don't want to keep anybody out. I just would like to use the core > packages of Debian release xyz (all the essential packages, for example) > together with more up-to-date packages in testing (kernel & drivers, > development tools, eye candy, games, etc). Well, I'm afr

Portability improvements with libbsd 0.3.0

2011-06-04 Thread Guillem Jover
Hi! One of the main motivations when creating the libbsd library was to ease porting source code with strong BSD origins by needing to patch them less, and to reduce code duplication in other projects. So if there are functions, macros or declarations commonly found on the BSDs that your packages

Re: distinguish between "core" and "main"?

2011-06-04 Thread Harald Dunkel
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/04/11 09:05, Paul Wise wrote: > Alternatively you might want to install from testing directly. Not > everything from testing is installable on stable, which is where > backports comes in. Installing testing for the whole system is no option. The

Re: distinguish between "core" and "main"?

2011-06-04 Thread Andrei POPESCU
On Sb, 04 iun 11, 10:12:42, Harald Dunkel wrote: > > I would prefer if Debian distinguishes between core and main instead. > This means splitting the current main repository. > > In the new system the main/testing packages should be _guaranteed_ > to work together with the most recent core/stable

Re: Bug#628953: O: mercurial-buildpackage -- Utillities for maintaining a deb package in Hg repository

2011-06-04 Thread Jens Peter Secher
On 2011-06-03 10:39, Andrew O. Shadoura wrote: > Jens, I always wanted to ask, why doesn't it sign the .dsc/.changes > files? It does not sign the result because I believe that signing a package should only happen after it has been tested, as a conscious decision. YMMV :-) Cheers, /JP signatur

Re: distinguish between "core" and "main"?

2011-06-04 Thread Neil Williams
On Sat, 04 Jun 2011 07:45:36 +0200 Harald Dunkel wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hi folks, > > Having 3+ packages within a single "main" repository is > pretty bulky. Would it be possible to distinguish between > the "core" Debian and "main" somehow? The princi

Re: distinguish between "core" and "main"?

2011-06-04 Thread Neil Williams
On Sat, 04 Jun 2011 10:12:42 +0200 Harald Dunkel wrote: > Installing testing for the whole system is no option. The base > system (the core packages) should be provided by the most recent > release. I don't want to get an unbootable system. You are more likely to get a problematic system by MIXI

Ok to use upstream doumentation as-is (i.e. not regenerate)?

2011-06-04 Thread Jonas Smedegaard
Hi fellow hackers, I have noticed several times package changes like the following (from cairomm entering testing today): * debian/control: - Drop build dependencies on doxygen and graphviz, since upstream now ships the generated documentation Feels wrong to me to redistribute whe

Re: Ok to use upstream doumentation as-is (i.e. not regenerate)?

2011-06-04 Thread Gergely Nagy
Jonas Smedegaard writes: > I have noticed several times package changes like the following (from > cairomm entering testing today): > > * debian/control: > - Drop build dependencies on doxygen and graphviz, since upstream > now ships the generated documentation > > > Feels wrong to

Re: Ok to use upstream doumentation as-is (i.e. not regenerate)?

2011-06-04 Thread Benjamin Drung
Am Samstag, den 04.06.2011, 14:10 +0200 schrieb Gergely Nagy: > Jonas Smedegaard writes: > > > I have noticed several times package changes like the following (from > > cairomm entering testing today): > > > > * debian/control: > > - Drop build dependencies on doxygen and graphviz, since u

Re: distinguish between "core" and "main"?

2011-06-04 Thread Harald Dunkel
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/04/11 07:26, Andrei POPESCU wrote: > > This is one of those recurrent discussions coming up on debian-devel. It > is my impression (as a lurker) that most Debian Developers do not want > to have second-class packages and it is a feature that a

Bug#629205: RFP: yelp -- When I use the help function for some Gnome program I get an error

2011-06-04 Thread Mats Olofsson
Package: yelp Severity: normal X-Debbugs-CC: debian-devel@lists.debian.org --- Please fill out the fields below. --- Package name: yelp Version: 2.30.1+webkit-1 (stable) Upstream Author: [NAME ] License: [GPL, LGPL, BSD, MIT/X, etc.] Description: [DESCRIPTION] When I use t

Re: Portability improvements with libbsd 0.3.0

2011-06-04 Thread Thorsten Glaser
Guillem Jover dixit: > pkg-config --cflags libbsd-overlay pkg-config is a GNU abomination and not used by BSD projects. >For existing packages using libbsd-dev (BCCed), several headers will >be removed in the upcoming 0.4.0 upstream release. To test that your >packages will keep building fine,

Re: distinguish between "core" and "main"?

2011-06-04 Thread Harald Dunkel
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Neil, On 06/04/11 12:36, Neil Williams wrote: > On Sat, 04 Jun 2011 10:12:42 +0200 > Harald Dunkel wrote: > >> Installing testing for the whole system is no option. The base >> system (the core packages) should be provided by the most recent >> r

Bug#629218: ITP: kamerka -- Take photos using your webcam and shiny animated QML interface

2011-06-04 Thread Sebastian Krzyszkowiak
Package: wnpp Severity: wishlist Owner: Sebastian Krzyszkowiak * Package name: kamerka Version : 0.6 Upstream Author : Sebastian Krzyszkowiak * URL : http://github.com/dos1/kamerka * License : GPLv2+ Programming Lang: C++ Description : Take photos usi

Re: distinguish between "core" and "main"?

2011-06-04 Thread brian m. carlson
On Sat, Jun 04, 2011 at 05:07:26PM +0200, Harald Dunkel wrote: > About the package set dependencies: The core package sets would be > self contained, i.e. they would not depend upon packages outside of > their own core set. The new main/testing repository would be meant > to work with both core/st

Re: distinguish between "core" and "main"?

2011-06-04 Thread Neil Williams
On Sat, 04 Jun 2011 17:07:26 +0200 Harald Dunkel wrote: > On 06/04/11 12:36, Neil Williams wrote: > > On Sat, 04 Jun 2011 10:12:42 +0200 > > Harald Dunkel wrote: > > > >> Installing testing for the whole system is no option. The base > >> system (the core packages) should be provided by the mos

Re: Ok to use upstream doumentation as-is (i.e. not regenerate)?

2011-06-04 Thread Bernhard R. Link
* Benjamin Drung [110604 14:22]: > It's better to build the pre-generated files from source in case you > need to modify the source. It's easier to just modify for example > configure.ac instead of modifying it and figuring out how to rebuild the > pre-generated files, especially when you do secur

Re: Portability improvements with libbsd 0.3.0

2011-06-04 Thread Bernhard R. Link
* Thorsten Glaser [110604 16:51]: > Guillem Jover dixit: > > > pkg-config --cflags libbsd-overlay > > pkg-config is a GNU abomination and not used by BSD projects. pkg-config is no GNU abomination, it'a a freedesktop thing. If it was a GNU abomination it would at least have gotten cflags vs cp

Re: Ok to use upstream doumentation as-is (i.e. not regenerate)?

2011-06-04 Thread Russ Allbery
"Bernhard R. Link" writes: > * Benjamin Drung [110604 14:22]: >> It's better to build the pre-generated files from source in case you >> need to modify the source. It's easier to just modify for example >> configure.ac instead of modifying it and figuring out how to rebuild >> the pre-generated

Re: Ok to use upstream doumentation as-is (i.e. not regenerate)?

2011-06-04 Thread Gergely Nagy
Benjamin Drung writes: > Am Samstag, den 04.06.2011, 14:10 +0200 schrieb Gergely Nagy: >> Jonas Smedegaard writes: >> >> > I have noticed several times package changes like the following (from >> > cairomm entering testing today): >> > >> > * debian/control: >> > - Drop build dependencie

[ANNOUNCE] dh_splitpackage 0.2.2

2011-06-04 Thread Zygmunt Krynicki
Hello everyone. I'd like to announce a new version of dh_splitpackage. This version improves documentation to a point where it's rather easy to get started and use this helper while packaging. A new manual page has been created with tool description documentation of all the command line optio

Re: Ok to use upstream doumentation as-is (i.e. not regenerate)?

2011-06-04 Thread Jonas Smedegaard
On 11-06-04 at 11:29am, Russ Allbery wrote: > "Bernhard R. Link" writes: > > * Benjamin Drung [110604 14:22]: > > >> It's better to build the pre-generated files from source in case > >> you need to modify the source. It's easier to just modify for > >> example configure.ac instead of modifyin

Re: [ANNOUNCE] dh_splitpackage 0.2.2

2011-06-04 Thread Benjamin Drung
Am Samstag, den 04.06.2011, 20:46 +0200 schrieb Zygmunt Krynicki: > The new script can be called instead of dh_install (assuming all the > files you are interested in are already in debian/tmp/) or afterwards. I looked at the man page of dh_splitpackage and compared it to "dh_install --fail-missi

Bug#629249: ITP: indicator-me -- indicator showing user information and status

2011-06-04 Thread Evgeni Golov
Package: wnpp Severity: wishlist Owner: The Ayatana Packagers * Package name: indicator-me Version : 0.2.19 Upstream Author : Ted Gould * URL : https://launchpad.net/indicator-me * License : GPL-3 Programming Lang: C Description : indicator showing use

Re: [ANNOUNCE] dh_splitpackage 0.2.2

2011-06-04 Thread Zygmunt Krynicki
W dniu 04.06.2011 21:59, Benjamin Drung pisze: Am Samstag, den 04.06.2011, 20:46 +0200 schrieb Zygmunt Krynicki: The new script can be called instead of dh_install (assuming all the files you are interested in are already in debian/tmp/) or afterwards. I looked at the man page of dh_splitpacka

Re: Bug#629249: ITP: indicator-me -- indicator showing user information and status

2011-06-04 Thread Josselin Mouette
Le samedi 04 juin 2011 à 22:52 +0200, Evgeni Golov a écrit : > It requires some way to be hosted into a panel. For the GNOME Panel the > appropriate package is indicator-applet-session. Has it been ported to the new GNOME Panel API? Because I don’t see anything in experimental. If it’s not port

Re: Bug#629249: ITP: indicator-me -- indicator showing user information and status

2011-06-04 Thread Evgeni Golov
On 06/04/2011 11:02 PM, Josselin Mouette wrote: > Le samedi 04 juin 2011 à 22:52 +0200, Evgeni Golov a écrit : >> It requires some way to be hosted into a panel. For the GNOME Panel the >> appropriate package is indicator-applet-session. > > Has it been ported to the new GNOME Panel API? Becaus

Re: [Pkg-ayatana-devel] Bug#629249: ITP: indicator-me -- indicator showing user information and status

2011-06-04 Thread Evgeni Golov
On 06/04/2011 11:13 PM, Evgeni Golov wrote: > On 06/04/2011 11:02 PM, Josselin Mouette wrote: >> Le samedi 04 juin 2011 à 22:52 +0200, Evgeni Golov a écrit : >>> It requires some way to be hosted into a panel. For the GNOME Panel the >>> appropriate package is indicator-applet-session. >> >> Has

Re: Ok to use upstream doumentation as-is (i.e. not regenerate)?

2011-06-04 Thread Tshepang Lekhonkhobe
On Sat, 2011-06-04 at 14:10 +0200, Gergely Nagy wrote: > (Provided that said action does not cause unwanted side effects, like > the documentation being out of date, because upstream forgot to > regenerate them before distribution - but that falls under the "upstream > to not be a moron" above ;)

Re: Bug#628042: perl: file creation in suid Perl script no longer works

2011-06-04 Thread Dominic Hargreaves
clone 628042 -1 reassign -1 release-notes retitle -1 release-notes: document that suidperl is no longer available in wheezy thanks On Fri, May 27, 2011 at 03:04:49PM +0300, Niko Tyni wrote: > On Fri, May 27, 2011 at 11:33:57AM +0100, Dominic Hargreaves wrote: > > > Upstream removed suidperl supp

Re: distinguish between "core" and "main"?

2011-06-04 Thread Tshepang Lekhonkhobe
On Sat, 2011-06-04 at 08:54 +0200, Harald Dunkel wrote: > On 06/04/11 07:56, Paul Wise wrote: > > Sounds like you are looking for backports.debian.org? > > > > Backports for Squeeze contains just about 400 package, > AFIACS. Would this be good enough for you if there were thousands of packages i

Re: Ok to use upstream doumentation as-is (i.e. not regenerate)?

2011-06-04 Thread Steve Langasek
On Sat, Jun 04, 2011 at 11:54:00PM +0200, Tshepang Lekhonkhobe wrote: > On Sat, 2011-06-04 at 14:10 +0200, Gergely Nagy wrote: > > (Provided that said action does not cause unwanted side effects, like > > the documentation being out of date, because upstream forgot to > > regenerate them before dis

Rolling release prototype

2011-06-04 Thread Josselin Mouette
Hi, I have prepared a quick and dirty implementation for my rolling release proposal[1]. I don’t think there is any need to make it cleaner; once we have convinced the FTP masters to include it in dak, the implementation will be trivial anyway (dak only needs a packages/archs/versions list). The

Re: Ok to use upstream doumentation as-is (i.e. not regenerate)?

2011-06-04 Thread Tshepang Lekhonkhobe
On Sat, 2011-06-04 at 16:16 -0700, Steve Langasek wrote: > On Sat, Jun 04, 2011 at 11:54:00PM +0200, Tshepang Lekhonkhobe wrote: > > On Sat, 2011-06-04 at 14:10 +0200, Gergely Nagy wrote: > > > (Provided that said action does not cause unwanted side effects, like > > > the documentation being out o

Re: Ok to use upstream doumentation as-is (i.e. not regenerate)?

2011-06-04 Thread Paul Wise
I'm leaning towards regenerating all mechanically generated files (including autotools stuff). I think it helps us live up to our promises (SC items 1-4, DFSG item 2). As an example of what I mean; the game naev was proposed to be added to Debian. Looking at the images I noted that some of them lo

Re: Ok to use upstream doumentation as-is (i.e. not regenerate)?

2011-06-04 Thread Vincent Bernat
On Sat, 4 Jun 2011 21:54:11 +0200, Jonas Smedegaard wrote: What I do is use upstream provided tarballs, then put aside autotools-generated files, then autogenerate myself, and in the clean rule put back the upstream-provided files (because I want not only minimal required build routines idempote

Re: [ANNOUNCE] dh_splitpackage 0.2.2

2011-06-04 Thread Vincent Bernat
On Sat, 04 Jun 2011 22:56:24 +0200, Zygmunt Krynicki wrote: [libfoo-dev] include=**/*.h include=**/*.la include=**/*.a # Just for demonstration, never pick any shared objects exclude=**/*.so I know this is just an exemple to show exclude but .so files have to be put in -dev packages. Exclude

Re: distinguish between "core" and "main"?

2011-06-04 Thread Harald Dunkel
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Neil, On 06/04/11 19:01, Neil Williams wrote: > > Testing compatibility is the larger problem. Automated tests can only > go so far. Dependencies are one thing, bugs which arise because one > setup is using a version which has already been replace