On Jun 06, Pirate Praveen wrote:
> - setup gitlab.debian.net on jessie with my personal repo added.
> - how do I add a machine?
> - Do we have a preferred hosting provider?
> - move to gitlab.debian.org after stretch release.
Can we use gitlab.debian.org from the beginning even if DSA is not
[copying dsa]
On Thursday 11 February 2016 05:47 PM, IOhannes m zmölnig (Debian/GNU)
wrote:
>
> thank you very much for all your efforts!
>
> now i only need a migration plan :-)
With gitlab 8.8.2 in the archive, I think we are ready to get it running
for debian. We have been running git.fossco
On Mon, Jun 06, 2016 at 02:50:51AM +0100, Ben Hutchings wrote:
> On Sun, 2016-06-05 at 18:41 -0700, Josh Triplett wrote:
> > On Mon, Jun 06, 2016 at 02:22:18AM +0100, Ben Hutchings wrote:
> > > On Sun, 2016-06-05 at 12:22 -0700, Josh Triplett wrote:
> > > > [Please CC me on replies. Aside: in my p
On Sun, 2016-06-05 at 18:41 -0700, Josh Triplett wrote:
> On Mon, Jun 06, 2016 at 02:22:18AM +0100, Ben Hutchings wrote:
> > On Sun, 2016-06-05 at 12:22 -0700, Josh Triplett wrote:
> > > [Please CC me on replies. Aside: in my previous mail, I set both
> > > Mail-Followup-To and Reply-To to include
On Mon, Jun 06, 2016 at 02:22:18AM +0100, Ben Hutchings wrote:
> On Sun, 2016-06-05 at 12:22 -0700, Josh Triplett wrote:
> > [Please CC me on replies. Aside: in my previous mail, I set both
> > Mail-Followup-To and Reply-To to include myself. What mailer and mechanism
> > did
> > you use to repl
On Sun, 2016-06-05 at 12:22 -0700, Josh Triplett wrote:
> [Please CC me on replies. Aside: in my previous mail, I set both
> Mail-Followup-To and Reply-To to include myself. What mailer and mechanism
> did
> you use to reply that didn't look at either of those headers?]
Evolution, Reply to List
Am 05.06.2016 um 17:13 schrieb Ian Jackson:
> Russ Allbery writes ("Re: Dropping upstart jobs (or not)"):
>> I'd happily maintain upstart configuration in my packages forever if
>> people were actually maintaining it or developing it, but since that's not
>> happening, it's very hard to see how mai
[Please CC me on replies. Aside: in my previous mail, I set both
Mail-Followup-To and Reply-To to include myself. What mailer and mechanism did
you use to reply that didn't look at either of those headers?]
Ben Hutchings wrote:
> On Sun, 2016-06-05 at 07:39 -0700, Josh Triplett wrote:
> > Ben Hu
Package: wnpp
Severity: wishlist
Owner: "Iain R. Learmonth"
* Package name: oonibackend
Version : 1.3.0
Upstream Author : OONI Developers
* URL : https://github.com/TheTorProject/ooni-backend
* License : BSD-2-clause
Programming Lang: Python
Description
Package: wnpp
Severity: wishlist
Owner: picca
* Package name: python-qtconsole
Version : 4.2.1
Upstream Author : Jupyter Development Team
* URL : https://github.com/jupyter/qtconsole
* License : BSD-3-clause
Programming Lang: Python
Description : enhanc
On Sun, 2016-06-05 at 16:08 +0100, Ian Jackson wrote:
> Ben Hutchings writes ("Detecting install vs upgrade in postinst"):
> > The postinst script for linux-image-* behaves differently on fresh
> > installation vs upgrade. For a fresh installation, it updates the
> > default symlinks /vmlinuz and
On Sun, 2016-06-05 at 07:39 -0700, Josh Triplett wrote:
> Ben Hutchings wrote:
> > On Sun, 2016-06-05 at 11:29 +0200, Marco d'Itri wrote:
> > > On Jun 05, Ben Hutchings wrote:
> > > > The postinst script for linux-image-* behaves differently on fresh
> > > > installation vs upgrade. For a fresh i
Russ Allbery writes ("Re: Dropping upstart jobs (or not)"):
> I'd happily maintain upstart configuration in my packages forever if
> people were actually maintaining it or developing it, but since that's not
> happening, it's very hard to see how maintaining configuration for a dead
> init system i
Ben Hutchings writes ("Detecting install vs upgrade in postinst"):
> The postinst script for linux-image-* behaves differently on fresh
> installation vs upgrade. For a fresh installation, it updates the
> default symlinks /vmlinuz and /initrd.img to point to the new kernel
> and initramfs version
Ben Hutchings wrote:
> On Sun, 2016-06-05 at 11:29 +0200, Marco d'Itri wrote:
> > On Jun 05, Ben Hutchings wrote:
> > > The postinst script for linux-image-* behaves differently on fresh
> > > installation vs upgrade. For a fresh installation, it updates the
> > > default symlinks /vmlinuz and /i
On Sun, 2016-06-05 at 11:29 +0200, Marco d'Itri wrote:
> On Jun 05, Ben Hutchings wrote:
>
> > The postinst script for linux-image-* behaves differently on fresh
> > installation vs upgrade. For a fresh installation, it updates the
> > default symlinks /vmlinuz and /initrd.img to point to the ne
On Jun 05, Jonathan Ulrich Horn wrote:
> > I'm rather wondering
> > how to deal with an ecosystem where it seems to be normal to release
> > tiny tiny packages…
> I ask myself more and more if it does make sense to have those tiny
> packages in debian.
Me too, also considering that I expect that
2016-06-05 12:25 GMT+02:00 Jonathan Ulrich Horn :
> Hey,
>
> On 06/05/2016 10:13 AM, Holger Levsen wrote:
> > I'm rather wondering
> > how to deal with an ecosystem where it seems to be normal to release
> > tiny tiny packages…
> I ask myself more and more if it does make sense to have those tiny
Hey,
On 06/05/2016 10:13 AM, Holger Levsen wrote:
> I'm rather wondering
> how to deal with an ecosystem where it seems to be normal to release
> tiny tiny packages…
I ask myself more and more if it does make sense to have those tiny
packages in debian.
> I've no idea what to do here
Well, one op
❦ 5 juin 2016 10:13 CEST, Holger Levsen :
> this is not about these two specific packages, I'm rather wondering
> how to deal with an ecosystem where it seems to be normal to release
> tiny tiny packages… (*)
>
> On Sun, Jun 05, 2016 at 03:25:48AM +0200, Jonathan Ulrich Horn wrote
> "Bug#82637
On Jun 05, Ben Hutchings wrote:
> The postinst script for linux-image-* behaves differently on fresh
> installation vs upgrade. For a fresh installation, it updates the
> default symlinks /vmlinuz and /initrd.img to point to the new kernel
> and initramfs versions. On upgrade it generally doesn
Package: wnpp
Owner: Remi Vanicat
Severity: wishlist
* Package name: elpa-tablist
Version : 0.70
Upstream Author : Andreas Politz
* URL or Web page : https://github.com/politza/tablist
* License : GPL3+
Description : tablist it an Emacs package that adds maks and fi
Package: wnpp
Owner: Remi Vanicat
Severity: wishlist
* Package name: pdf-tools
Version : 0.70
Upstream Author : Andreas Politz
* URL or Web page : https://github.com/politza/pdf-tools
* License : GPL V3+
Description : Display and interact with pdf in Emacs.
This mo
Hi,
this is not about these two specific packages, I'm rather wondering
how to deal with an ecosystem where it seems to be normal to release
tiny tiny packages… (*)
On Sun, Jun 05, 2016 at 03:25:48AM +0200, Jonathan Ulrich Horn wrote
"Bug#826371: ITP: node-camelcase-keys -- Convert object keys t
24 matches
Mail list logo
