Bug#620332: ITP: naspro-bridges -- collection of bridges to LV2
Package: wnpp Severity: wishlist Owner: Alessio Treglia * Package name: naspro-bridges Version : 0.2.90 Upstream Author : Stefano D'Angelo * URL : http://naspro.atheme.org/naspro-bridges * License : LGPL Programming Lang: C Description : collection of bridges to LV2 NASPRO bridges is a collection of bridges to LV2 which, once installed, allow users to use plugins developed for other plugin standards in LV2 hosts. . This release contains two such bridges: a LADSPA (+ LRDF) and a DSSI one. . The LADSPA bridge supports every feature of LADSPA and LRDF except: * run_adding() and set_run_adding_gain(). * LRDF factory presets. The DSSI bridge does not support: * GUIs; * MIDI banks and programs; * maximum number of events per run_synth() - it is 4096, should be enough in most cases; * run_synth_adding() - as before; * run_multiple_synths() and run_multiple_synths_adding() - no extension to do that and it may also be impossible to support those. -- 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/20110401071509.10557.84385.reportbug@alessio-laptop
Bug#620333: ITP: naspro-bridge-it -- library to develop insert-your-API-here to LV2 bridges
Package: wnpp Severity: wishlist Owner: Alessio Treglia * Package name: naspro-bridge-it Version : 0.2.90 Upstream Author : Stefano D'Angelo * URL : http://naspro.atheme.org/naspro-bridge-it/ * License : LGPL Programming Lang: C Description : library to develop API-to-LV2 bridges NASPRO Bridge it is a little helper library to develop insert-your-API-here to LV2 bridges. . As of now, it basically offers a few utility functions and Turtle/RDF serialization for LV2 dynamic manifest generation, supporting the following LV2 specifications/extensions: * LV2 revision 4.0; * LV2 Dynamic Manifest revision 1.0; * Extended Port Information draft revision 3 (only for the logarithmic port property); * LV2 Events revision 1.0; * LV2 MIDI Events revision 1.0. . It is written in C99 and is almost entirely reentrant and thread-safe. -- 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/20110401073721.13271.21686.reportbug@alessio-laptop
Re: dh_shlibdeps warnings concerning undefined OpenMP symbols
On 31.03.2011 22:16, Jakub Wilk wrote:
>> You do need -lgomp.
>
> You normally don't (need to) link to gomp explicitly. My wild guess is:
> Dmitry used -fopenmp while compiling *.o, but not when linking the
> shared library.
Exactly! Thank you, Jakub, for nice guess.
AC_OPENMP() macro documentation looks to be a bit incomplete (e.g. if it
provides $OPENMP_LDFLAGS I wouldn't mess things), so I believe the
correct sequence looks like this:
AC_OPENMP()
CPPFLAGS="${OPENMP_CFLAGS} ${CPPFLAGS}"
CXXFLAGS="${OPENMP_CXXFLAGS} ${CXXFLAGS}"
LDFLAGS="${OPENMP_CXXFLAGS} ${LDFLAGS}"
I also was suggested this resource:
> http://wiki.debian.org/ToolChain/DSOLinking#Unresolved_symbols_in_shared_libraries
which explains that this warning is raised, when the dependency chain is
like "A -> B -> C", and A needs symbols from C, but has no direct
dependency "A -> C" (which should be introduced as Brian also mentioned).
Thanks a lot for help.
--
With best regards,
Dmitry
--
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/4d958b0b.1010...@mail.ru
Re: Support for SMACK security framework
Hello Russell and Christian, Russell Coker wrote on 2011-04-01 10:19: > > If you need some tips then I will be happy to offer some. I can also host > some developer resources if you need it (we can discuss that off-list). Thank you for your offer for tips and resources. > But you really have to just do it. I didn't know much about "security > frameworks" before I started working on SE Linux. So it seems I have chances to learn it, too. > As SE Linux has significantly less than 50% user-share in Debian that leaves > plenty of scope for you to find some SMACK users. :-# That is my thought, too. "Christian Pohl" wrote on 2011-04-01 08:27: > > I would help you with installing and testing and Thank you for your offer. Then I want to start with maintainance of smack utilities. Thank you very much for your feedback! --- 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/20110401103017.4f010...@jupiter.home
hurd 0.401 is released!
Hello, There are rumors that Duke Nukem Forever will actually be released in Apr^WMa^WJune 2011, so there's no escape for the Hurd any more, we had to finish and release. There has been considerable progress lately, so it is with great pleasure that the Hurd maintainers team decided to release version 0.401 of the GNU/Hurd Operating System. As the version number and image size suggest, this is only a small preview of course, but we expect GNU/Hurd to be of production-quality within the third millenium, to be sure. A LiveCD demo is available on http://people.debian.org/~sthibault/hurd-0.401/hurd-0.401.iso and can be trivially tried using qemu -cdrom hurd-0.401.iso We hope that you will appreciate its features and speed. Are you interested in contributing to the GNU Hurd project? Just request an shell account on one of our servers and get started. http://www.gnu.org/software/hurd/public_hurd_boxen.html It is also worth noting that like in previous years, GNU/Hurd runs for the GSoC program, details can be found on http://www.gnu.org/software/hurd/community/gsoc.html -- 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/20110401083832.gd4...@const.bordeaux.inria.fr
Re: "expected stable-updates but got squeeze-updates"
On Thu, 31, Mar, 2011 at 08:25:38AM +, Philipp Kern spoke thus..
> On 2011-03-30, Adam D. Barratt wrote:
> > However, having "squeeze" in sources.list whilst the Release file
> > contains "stable" works okay, so I assume apt is managing the
> > translation internally in that case.
>
> Nah, that's the bug we received and then assigned to ftp-master, which didn't
> fix it yet:
>
> pkern@franck:~/ftp/ftp/dists$ egrep -i '(codename|suite)'
> squeeze{,-updates}/Release
> squeeze/Release:Suite: stable
> squeeze/Release:Codename: squeeze
> squeeze-updates/Release:Suite: squeeze-updates
> squeeze-updates/Release:Codename: squeeze-updates
I've put a temporary hack in place in generate-releases to fix this for
now until we change dak/projectb to use the codenames instead of suite
names for the main suites. Should be live as of the next dinstall.
I'm keeping the bug open for now until it's fixed properly.
Mark
--
Mark Hymers
"I told you I was ill"
The epitaph of Spike Milligan (1918-2002)
--
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/2011040200.ga14...@hymers.org.uk
Re: ifupdown and IPv6
On 31/03/2011 21:15, Andrew O. Shadoura wrote: > Hello, > > On Thu, 31 Mar 2011 00:01:25 +0200 > m...@linux.it (Marco d'Itri) wrote: > >> The problem is with all features implemented by external if-*.d >> scripts. If e.g. a bridge is created by the first defined afi, the >> second script will fail. And if it does not fail on up then >> everything will still break on a down event, when the script run by >> the first AFI will destroy the interface and ifupdown will be able to >> remove the IP address of the second AFI. > > Can you run into details a bit? Try to define a setup where you have a bridged interface with IPv4 and IPv6 and you want to up/down separately in any order the IPv4 setup and the IPv6 setup. Is is very difficult to know when the bridge must be enabled and disabled for example. Regards, Vincent -- Vincent Danjean GPG key ID 0x9D025E87 vdanj...@debian.org GPG key fingerprint: FC95 08A6 854D DB48 4B9A 8A94 0BF7 7867 9D02 5E87 Unofficial packages: http://moais.imag.fr/membres/vincent.danjean/deb.html APT repo: deb http://people.debian.org/~vdanjean/debian unstable main -- 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/4d95c625.5060...@free.fr
Re: dh_shlibdeps warnings concerning undefined OpenMP symbols
On 01/04/2011 10:21, Dmitry Katsubo wrote: > On 31.03.2011 22:16, Jakub Wilk wrote: >>> You do need -lgomp. >> >> You normally don't (need to) link to gomp explicitly. My wild guess is: >> Dmitry used -fopenmp while compiling *.o, but not when linking the >> shared library. > > Exactly! Thank you, Jakub, for nice guess. > AC_OPENMP() macro documentation looks to be a bit incomplete (e.g. if it > provides $OPENMP_LDFLAGS I wouldn't mess things), Please, report a bug for this macro if it is provided by another package. Regards, Vincent -- Vincent Danjean GPG key ID 0x9D025E87 vdanj...@debian.org GPG key fingerprint: FC95 08A6 854D DB48 4B9A 8A94 0BF7 7867 9D02 5E87 Unofficial packages: http://moais.imag.fr/membres/vincent.danjean/deb.html APT repo: deb http://people.debian.org/~vdanjean/debian unstable main -- 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/4d95c750.9080...@free.fr
Re: oldstable-security signing key
On Sat, 26, Mar, 2011 at 09:02:46AM +, Mark Hymers spoke thus.. > If anyone has any objections to this, can they let us know? I intend to > implement the changes necessary to make this work in dak immediately, > but won't change the key over for a couple of days to give people time > to raise objections. Hi, This has now been done. Mark -- Mark Hymers "Don't you hate those Claims Direct adverts? 'I slipped on a banana skin and sued the Dominican Republic!'" Linda Smith on the News Quiz talking about the Compensation Culture -- 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/20110401125050.ga19...@hymers.org.uk
Re: /run support for wheezy?
On Wed, Mar 30, 2011 at 11:20:45PM +0100, Roger Leigh wrote: > On Wed, Mar 30, 2011 at 10:32:51PM +0200, Goswin von Brederlow wrote: > > Tollef Fog Heen writes: > > > > > ]] Julien Cristau > > > > > > | On Wed, Mar 30, 2011 at 16:20:10 +0100, Roger Leigh wrote: > > > | > > > | > Given that Fedora are adopting /run, and it has been something > > > | > we have wanted in the past, is anyone working on implementing > > > | > /run in Debian? > > > | > > > > | > http://thread.gmane.org/gmane.linux.redhat.fedora.devel/146976 > > > > > > Incidentially, I just sent a mail proposing this as a release goal. > > > > > > | That seems to say "on Debian /lib/init/rw was introduced for the same > > > | thing, but I'm using a different name just because I can". What am I > > > | missing? > > > > > > It's a bit of an abuse of the /lib namespace. It also outlines a plan > > > for how to get rid of /var/run and /var/lock long-term, something I > > > don't believe /lib/init/rw ever tried to. It was just somewhere to > > > stuff random early data. > > > > What subdirs will we have then? > > > > /run/run (formerly /var/run) > > /run/init (formerly /lib/init/rw) > > /run/lock (formerly /var/lock) > > > > or will one of the formerlies become the /run and the other subdirs. or > > will /var/run and /lib/init/rw be merged into just /run and /run/lock > > for locks? > > I've filed a bug (#620191) against initscripts containing a proposed > patch for this. > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=620191 > > /var/run (→ /run) > /var/lock (→ /run/lock) > /lib/init/rw (→ /run/init) OK, an update on progress implementing /run: Patches filed against base-files and initscripts in #620157 and #620191. Test packages here: http://people.debian.org/~rleigh/run/ (tested in an amd64 kvm VM; it shouldn't toast your system by making it unbootable, but YMMV; test with caution.) There's a couple of outstanding issues which I could use some help with: 1) /etc/init.d/mountall.sh is broken for some reason. The "mount -a" invocation fails. Not because it fails to mount, but it returns a 32 exit status because / and /proc are already mounted. Possibly a result of the mtab.sh domtab() changes; but it should be behaving identically to the old version, so possibly unrelated. Possibly already broken and I've just exposed a bug? 2) Despite only mounting /run once, I'm seeing /run and /run/lock mounted *again* looking at /proc/mounts. Unsure why this happens, or if it's just artifactual. /run, /run/lock and /run/init are all correctly visible, but this is a tad strange. I would also appreciate any testing, especially if you're using a nonstandard setup e.g. tmpfs on /var/run and/or /var/lock. This should be catered for. Testing on kfreebsd would also be welcome, since the mtab changes were done to make bind mounting work for it. Regards, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linux http://people.debian.org/~rleigh/ `. `' Printing on GNU/Linux? http://gutenprint.sourceforge.net/ `-GPG Public Key: 0x25BFB848 Please GPG sign your mail. signature.asc Description: Digital signature
Re: /run support for wheezy?
Hi there! On Fri, 01 Apr 2011 15:33:44 +0200, Roger Leigh wrote: > Patches filed against base-files and initscripts in #620157 and #620191. > Test packages here: http://people.debian.org/~rleigh/run/ > (tested in an amd64 kvm VM; it shouldn't toast your system by > making it unbootable, but YMMV; test with caution.) [...] > I would also appreciate any testing, especially if you're using a > nonstandard setup e.g. tmpfs on /var/run and/or /var/lock. Without having looked/tested your packages and being a bit naive, but given that tmpfs for /var/run and /var/lock can be configured through /etc/default/rcS, maybe it is more used than you think (and I would not completely call it nonstandard), thus it requires a bit more caution. Thx, bye, Gismo / Luca pgp51RaMgemW0.pgp Description: PGP signature
Re: /run support for wheezy?
On Fri, Apr 01, 2011 at 02:33:44PM +0100, Roger Leigh wrote: > On Wed, Mar 30, 2011 at 11:20:45PM +0100, Roger Leigh wrote: > > On Wed, Mar 30, 2011 at 10:32:51PM +0200, Goswin von Brederlow wrote: > > > Tollef Fog Heen writes: > > > > > > > ]] Julien Cristau > > > > > > > > | On Wed, Mar 30, 2011 at 16:20:10 +0100, Roger Leigh wrote: > > > > | > > > > | > Given that Fedora are adopting /run, and it has been something > > > > | > we have wanted in the past, is anyone working on implementing > > > > | > /run in Debian? > > > > | > > > > > | > http://thread.gmane.org/gmane.linux.redhat.fedora.devel/146976 > > > > > > > > Incidentially, I just sent a mail proposing this as a release goal. > > > > > > > > | That seems to say "on Debian /lib/init/rw was introduced for the same > > > > | thing, but I'm using a different name just because I can". What am I > > > > | missing? > > > > > > > > It's a bit of an abuse of the /lib namespace. It also outlines a plan > > > > for how to get rid of /var/run and /var/lock long-term, something I > > > > don't believe /lib/init/rw ever tried to. It was just somewhere to > > > > stuff random early data. > > > > > > What subdirs will we have then? > > > > > > /run/run (formerly /var/run) > > > /run/init (formerly /lib/init/rw) > > > /run/lock (formerly /var/lock) > > > > > > or will one of the formerlies become the /run and the other subdirs. or > > > will /var/run and /lib/init/rw be merged into just /run and /run/lock > > > for locks? > > > > I've filed a bug (#620191) against initscripts containing a proposed > > patch for this. > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=620191 > > > > /var/run (→ /run) > > /var/lock (→ /run/lock) > > /lib/init/rw (→ /run/init) > > OK, an update on progress implementing /run: > > Patches filed against base-files and initscripts in #620157 and #620191. > Test packages here: http://people.debian.org/~rleigh/run/ > (tested in an amd64 kvm VM; it shouldn't toast your system by > making it unbootable, but YMMV; test with caution.) > > There's a couple of outstanding issues which I could use some help > with: These last issues have been resolved now, so the packages at the above URL should be safe for general testing and use. > I would also appreciate any testing, especially if you're using a > nonstandard setup e.g. tmpfs on /var/run and/or /var/lock. This should > be catered for. Testing on kfreebsd would also be welcome, since the > mtab changes were done to make bind mounting work for it. Testing is still very much needed. Thanks, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linux http://people.debian.org/~rleigh/ `. `' Printing on GNU/Linux? http://gutenprint.sourceforge.net/ `-GPG Public Key: 0x25BFB848 Please GPG sign your mail. signature.asc Description: Digital signature
Re: /run support for wheezy?
On Fri, Apr 01, 2011 at 04:06:16PM +0200, Luca Capello wrote:
> Hi there!
>
> On Fri, 01 Apr 2011 15:33:44 +0200, Roger Leigh wrote:
> > Patches filed against base-files and initscripts in #620157 and #620191.
> > Test packages here: http://people.debian.org/~rleigh/run/
> > (tested in an amd64 kvm VM; it shouldn't toast your system by
> > making it unbootable, but YMMV; test with caution.)
> [...]
> > I would also appreciate any testing, especially if you're using a
> > nonstandard setup e.g. tmpfs on /var/run and/or /var/lock.
>
> Without having looked/tested your packages and being a bit naive, but
> given that tmpfs for /var/run and /var/lock can be configured through
> /etc/default/rcS, maybe it is more used than you think (and I would not
> completely call it nonstandard), thus it requires a bit more caution.
Not entirely sure what you mean here. We detect and deal with this
sort of setup automatically. I said "nonstandard" because TTBOMK this
feature is not widely used, and (I am given to understand) somewhat
broken. I have tested this with manual mounts, and the code is working
for me. Caution is definitely warranted though--that's why I'd like
more widespread testing so we can identify any special cases we need
to deal with in addition (if any).
If you're using RAMRUN/RAMLOCK, then you'll get the same setup, but
mounted under /run and /run/lock, with compatibility symlinks in place.
If you've set up the tmpfs mounts manually in /etc/fstab, we create
bind mounts on top since we can't create the symlinks. It will again
automatically transition when you remove the fstab entries and reboot
(or you can just remove the entries, unmount the filesystems and rerun
the mountall init script).
AFAICT, we now cater for transitioning of all previously supported
configurations, as well as unsupported (manual) setups, though if you
manually set up stuff, you'll have to manually undo your work to clean
up properly (though you'll have a fully functional system at all times).
The logic is in run_migrate() in /lib/init/mount-functions.sh called
after mounting local filesystems in /etc/init.d/mountall.sh:
#
# Migrate a directory to /run and create compatibility symlink or bind
# mount.
#
run_migrate ()
{
OLD=$1
RUN=$2
KERNEL="$(uname -s)"
OPTS=""
case "$KERNEL" in
Linux|GNU) FSTYPE=none OPTS="-obind";;
*FreeBSD) FSTYPE=nullfs ;;
*) FSTYPE=none ;;
esac
# Try to remove if a directory. Note this is safe because the
# system is not yet fully up, and nothing is allowed to use
# them yet. If the user explicitly mounted a filesystem here,
# it will be cleaned out, but this would happen later on when
# bootclean runs in any case.
if [ ! -L "$OLD" ] && [ -d "$OLD" ] ; then
rm -fr "$OLD" 2>/dev/null || true
fi
# If removal failed (directory still exists), set up bind mount.
if [ ! -L "$OLD" ] && [ -d "$OLD" ] ; then
mount -t $FSTYPE "$RUN" "$OLD" -orw $OPTS
else
# Create symlink if not already present.
if [ -L "$OLD" ] && [ "$(readlink "$OLD")" = "$RUN" ]; then
:
else
ln -fs "$RUN" "$OLD"
fi
fi
}
#
# For compatibility, create /var/run and /var/lock symlinks to /run
# and /run/lock, respectively.
#
post_mountall ()
{
# /var/run and /var/lock are now /run and /run/lock,
# respectively. Cope with filesystems being deliberately
# mounted on /var/run and /var/lock. We will create bind
# mounts from /run and /run/lock to /var/run and /var/lock if
# we can't remove the /var/run and /var/lock directories, or
# else simply create symlinks. For example, in the case that
# the user has explicitly mounted filesystems on /var/run or
# /var/lock, we bind mount over the top of them. Where no
# filesystems are mounted, we replace the directory with a
# symlink where possible.
run_migrate /var/run /run
run_migrate /var/lock /run/lock
}
Regards,
Roger
--
.''`. Roger Leigh
: :' : Debian GNU/Linux http://people.debian.org/~rleigh/
`. `' Printing on GNU/Linux? http://gutenprint.sourceforge.net/
`-GPG Public Key: 0x25BFB848 Please GPG sign your mail.
signature.asc
Description: Digital signature
Re: Bug#510415: Call for votes on Bug#510415: tech-ctte: Qmail inclusion (or not) in Debian
On Fri, 01 Apr 2011, Mark Hymers wrote: > On Tue, 29, Mar, 2011 at 08:14:21AM -0700, Don Armstrong spoke thus.. > > What is the current status of this? > > I've just checked the packages, and given the constraints of #510415, I > have accepted netqmail, dot-forward, fastforward, qmail-run and > qmail-tools. I will shortly be filing RC bugs against each of these as > per #510415 to prevent their migration to testing. Once I have those > bug numbers, I will update #510415 appropriately. Awesome; thanks Mark! Just a heads up for those on -devel who had additional bugs that were reported to the CTTE; these should be filed against the appropriate qmail package if they are still an issue. Don Armstrong -- First you take a drink, then the drink takes a drink, then the drink takes you. -- F. Scott Fitzgerald http://www.donarmstrong.com http://rzlab.ucr.edu -- 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/20110401163455.gi23...@teltox.donarmstrong.com
Re: dh_shlibdeps warnings concerning undefined OpenMP symbols
* Vincent Danjean , 2011-04-01, 14:38: AC_OPENMP() macro documentation looks to be a bit incomplete (e.g. if it provides $OPENMP_LDFLAGS I wouldn't mess things), Please, report a bug for this macro if it is provided by another package. I don't think there's anything wrong with this macro. CXXFLAGS should be used both for compiling and linking. At least this is what GNU make do by default: $ make -p 2>/dev/null | grep 'LINK.cc = ' LINK.cc = $(CXX) $(CXXFLAGS) $(CPPFLAGS) $(LDFLAGS) $(TARGET_ARCH) -- Jakub Wilk -- 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/20110401124749.ga...@jwilk.net
Re: mlton any->all package transition breakage
On Thu, 31 Mar 2011, Wesley W. Terpstra wrote: > I request the above packages to be installed on these machines: > albeniz.debian.org alpha 8g y > abel.debian.org armel 1.5gy > merulo.debian.org ia648g y > asdfasdf.debian.net kfreebsd-amd64 2g y > ad...@asdfasdf.debian.net > io.debian.net kfreebsd-i386 1.5gy ad...@io.debian.net > gabrielli.debian.orgmips1.6gy > zelenka.debian.org s3901g y > smetana.debian.org sparc 2g y > I am looking for a solution to this build problem for mipsel and powerpc. If > the old mlton 'any' package (still in squeeze) were re-added to unstable, > that would work (and also render the above package installation requests > unnecessary). I'm open to any other suggestions. There is no squeeze on alpha, so there is no mlton package in squeeze on alpha. merulo's apt-get in sid now segfaults on apt-get update, after having read the squeeze packages list once. Nothing brings it back to live. all the other chroots are now fucked because we did as you asked, and for some reason it wants to bring in mlton-doc: | The following NEW packages will be installed: | mlton-doc | The following packages have been kept back: | mlton | 0 upgraded, 1 newly installed, 0 to remove and 1 not upgraded. | Need to get 3531 kB of archives. | After this operation, 7926 kB of additional disk space will be used. | Get:1 http://ftp.uk.debian.org/debian/ sid/main mlton-doc sparc 20100608-3 [3531 kB] | Fetched 3531 kB in 5s (613 kB/s) | debconf: delaying package configuration, since apt-utils is not installed | Selecting previously deselected package mlton-doc. | (Reading database ... 141241 files and directories currently installed.) | Unpacking mlton-doc (from .../mlton-doc_20100608-3_sparc.deb) ... | dpkg: error processing /var/cache/apt/archives/mlton-doc_20100608-3_sparc.deb (--unpack): | trying to overwrite '/usr/share/doc-base/mlton', which is also in package mlton 20100608-2 | configured to not write apport reports | dpkg-deb: subprocess paste killed by signal (Broken pipe) I think we won't be doing anything like that again any time soon. > PS. I could not determine which mailing list is haunted by the ftp-masters. ftpmaster can be reached at ftpmaster@d.o. debian-admin is debian admin (aka DSA). > If debian-admin is wrong, please forward it. no. -- | .''`. ** Debian ** Peter Palfrader | : :' : The universal http://www.palfrader.org/ | `. `' Operating System | `-http://www.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/20110401195833.gw...@anguilla.noreply.org
Re: mlton any->all package transition breakage
On Fri, Apr 1, 2011 at 9:58 PM, Peter Palfrader wrote: > all the other chroots are now fucked because we did as you asked, and > for some reason it wants to bring in mlton-doc The problem there is you're trying to install and/or upgrade the sid one, not the squeeze one. > I think we won't be doing anything like that again any time soon. Feel free to purge whatever mlton package you have installed. I've been fairly successful building the package from installing the .debs in my home directory.
Re: mlton any->all package transition breakage
On Fri, 01 Apr 2011, Wesley W. Terpstra wrote: > On Fri, Apr 1, 2011 at 9:58 PM, Peter Palfrader wrote: > > > all the other chroots are now fucked because we did as you asked, and > > for some reason it wants to bring in mlton-doc > > > The problem there is you're trying to install and/or upgrade the sid one, > not the squeeze one. No, the squeeze package installed cleanly. now apt-get update && upgrade breaks. That means the package is buggy. -- | .''`. ** Debian ** Peter Palfrader | : :' : The universal http://www.palfrader.org/ | `. `' Operating System | `-http://www.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/20110401204725.gy...@anguilla.noreply.org
Re: mlton any->all package transition breakage
On Fri, Apr 1, 2011 at 10:47 PM, Peter Palfrader wrote: > > The problem there is you're trying to install and/or upgrade the sid one, > > not the squeeze one. > > No, the squeeze package installed cleanly. now apt-get update && > upgrade breaks. That means the package is buggy. > Yes, I know it's buggy. That's why I'm trying to fix it. It is missing a replaces/breaks, which leads to upgrade problems. However, before I can upload a new version that fixes that, I need to get a working bootstrap version that the buildd will actually install.
invitation : meeting d'affaire
Rencontrer d'autres chefs d'entreprises Prospectez de nouvelles opportunités d'affaires ! L'association « Le Maroc Positif » vous invite à la 1ere Rencontre des chefs d'entreprises (200 décideurs sont invités) pour échanger directement entre eux leurs besoins et leurs offres ; ceci le 14 Avril au Centre d'Accueil et de Conférence (CAC) de Hay Riad Rabat à 15H30. Frais de Participation : 300dhs. Cette rencontre est une occasion à ne pas rater pour : · Rencontrer d'autres chefs d'entreprises et développer votre relationnel ; · Présenter votre entreprise et vos offres aux chefs d'entreprises participants ; · S'informer sur leurs besoins liés à votre secteur d'activité ; · S'informer aussi sur les différentes promotions proposées par les autres participants.. Bref, c'est votre rendez-vous mensuel, à marquer sur votre agenda, pour renforcer l'image de votre Sté et de développer vos affaires. http://www.exit.ma/14avril http://www.facebook.com/event.php?eid=214513301897801 Contact: Said ETEBBAI : 0671 20 40 91 Président de l'Association : Abdelhafid FAHMI au 0669146969 Responsable de programmation : Brahim Laaouina au 0661390064
Call for Testing: Unofficial Debian Monthly Testing Snapshot Release Candidate (version 2011.04rc1)
Hi, I am pleased to announce the unofficial Debian monthly testing snapshot release candidate for April 2011. This release is currently available in two flavors, i386 and amd64, as mini iso images (16 MiB each) downloadable from: http://alioth.debian.org/~gilbert-guest/snapshots/2011.04/debian-testing-snapshot-2011.04rc1-i386-mini.iso http://alioth.debian.org/~gilbert-guest/snapshots/2011.04/debian-testing-snapshot-2011.04rc1-amd64-mini.iso 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 The testing period will be 5 days, and if no showstoppers are found in that time frame, this will be the 2011.04 final release, which is currently targeted for April 6th. Since this is not a stable release, a much reduced subset of bugs will be considered showstopping (a different criteria than stable's release critical bugs). These only include: 1. Failure to install from scratch using default/common options 2. Failure to boot into a graphical environment There may be more criteria identified in the future. If you think an issue qualifies as a showstopping bug, please send a message to cut-t...@lists.alioth.debian.org, and we will determine whether it is worth delaying the release. If showstopper bugs are indeed found, then the previous month's nightly generated media will be bisected to find the one prior to introduction of the bug. That will be the second release candidate, and there will be another announcement and 5 day testing period for that. Note that these monthly snapshot releases will be guaranteed to be upgradable (all new releases will have >= package versions compared to the previous release). However, there is no guarantee that there won't be breakages or regressions in particular packages between upgrades. This may be somewhat solvable via automated piuparts upgrade testing in the future. This will need someone interested to work on this particular problem. IMPORTANT: release candidates will not necessarily be upgradable since subsequent versions may include packages that are older than those in the previous version. Please consider this carefully before installing from release candidate media on important machines. Note also that 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 another 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). 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. This message is being limited only to the debian-devel list to (hopefully) keep the load on existing resources small for now, and to determine whether a more robust hosting solution will be necessary for future releases. This also provides a chance for feedback and contributions from the devel community before attempting to target a wider audience. Please keep in mind that this is an unofficial test/development release before spreading the word too much. Anyway, enjoy! And send feedback to cut-t...@lists.alioth.debian.org. Best wishes, Mike Gilbert -- 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/20110401223508.3577a1ac.michael.s.gilb...@gmail.com
Re: Debian Project Leader Elections 2011: Call for votes
Debian wrote: > Hi, > > It seems I made a error in the first mail. The correct ballot > to reply to is: > - - -=-=-=-=-=- Don't Delete Anything Between These Lines > =-=-=-=-=-=-=-=- 0942471d-23ab-4b5e-b5a8-02c2e74cb588 > [ x ] Choice 1: Stefano Zacchiroli > [ ] Choice 2: None Of The Above > - - -=-=-=-=-=- Don't Delete Anything Between These Lines > =-=-=-=-=-=-=-=- > > > Kurt Roeckx > Debian Project Secretary > Cheers, Paul. -- 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/20110402170902.14664be9@frodo
Re: Debian Project Leader Elections 2011: Call for votes
Debian wrote: > Hi, > > It seems I made a error in the first mail. The correct ballot > to reply to is: > - - -=-=-=-=-=- Don't Delete Anything Between These Lines > =-=-=-=-=-=-=-=- 0942471d-23ab-4b5e-b5a8-02c2e74cb588 > [ x ] Choice 1: Stefano Zacchiroli > [ ] Choice 2: None Of The Above > - - -=-=-=-=-=- Don't Delete Anything Between These Lines > =-=-=-=-=-=-=-=- > > > Kurt Roeckx > Debian Project Secretary > Cheers, Paul. -- 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/20110402165220.5d32fb2f@frodo
Bug#620464: ITP: pygossip -- distributed domain reputation service
Package: wnpp Severity: wishlist Owner: Scott Kitterman * Package name: pygossip Version : 0.5 Upstream Author : Stuart Gathman * URL : http://pymilter.sourceforge.net/ * License : GPL-2 Programming Lang: Python Description : distributed domain reputation service GOSSiP systems track the ratio of spam to ham for each domain, and compute a reputation score from that. They also compute a confidence score that increases with the number and freshness of observations. . They can also check with peers, and combine scores. Observations are provided by a spam filter or user feedback. . Pygossip is a GOSSiP implementation. -- 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/20110402042518.23565.43740.reportbug@localhost6.localdomain6
Re: Debian Project Leader Elections 2011: Call for votes
Hi Paul, On Sat, 2 Apr 2011 17:09:02 +1300, Paul Waite wrote: > Debian wrote: > > - - -=-=-=-=-=- Don't Delete Anything Between These Lines > > =-=-=-=-=-=-=-=- 0942471d-23ab-4b5e-b5a8-02c2e74cb588 > > [ x ] Choice 1: Stefano Zacchiroli > > [ ] Choice 2: None Of The Above > > - - -=-=-=-=-=- Don't Delete Anything Between These Lines > > =-=-=-=-=-=-=-=- That's wrong. You should use "1" and "2" -- not "x". Also, you should send your vote to leader2...@vote.debian.org . Kindly, David -- . ''`. Debian developer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://deb.li/dapal `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature
