search for: dinstal

Hi, 0.99 is running nicely on my sarges, but I need pop3_uidl_format = %f for Courier compatibility. I can't find any debs more recent than test22 of over a year ago (those are at http://src.braincells.com/dovecot-test/). Even though google turns up http://hemma.tobbe.nu/debian/mini-dinstall/incoming/dovecot_1.0.test46-1_i386.changes searching for dovecot on packages.debian.org (any distribution or source) only yields 0.99.14 and 0.99.20050712. I know Jaldhar called for vounteers to take over, but I don't feel qualified... but I've managed to do away with all non-deb install...

...finate amount of revisions without making the version string considerably longer with multiple versions. Of course it would limit us to a daily build release. We also need not have to necessarially upload to the 'experimental' distro for testing but can host a mini-repository using the mini-dinstall package and even have it so anyone in the group could actually upload to that, whereas the official upload would need to be done by one of us with DD upload rights. As for the kernel patch build policy. As I've spoken with a few other DDs, the build should be self-contained and this not r...

Hi, I'm using Ubuntu 9.10 amd64 with cran2deb packages (I know it's meant for Debian, it's worked fine for me for many months). Recently apt-get update has to started to complain: ... Hit http://debian.cran.r-project.org testing/ Release Get:1 http://debian.cran.r-project.org testing/ Packages [515kB] Fetched 1B in 3s (0B/s) W: Failed to fetch

Announcing cran2deb: 1700+ Debian packages from almost all of CRAN ------------------------------------------------------------------ Last Friday's presentation at UseR! 2009 was the first really public mention of 'cran2deb'. It provides Debian packages of all of CRAN. It started as Charles' project from last year's Google Summer of Code, was further extended by us over the

...pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is rea...

...pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is rea...

...pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is rea...

...pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is rea...

...pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is rea...

...pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is rea...