Re: debian github organization ?

[Stuart Prescott]

Jonathan Dowland wrote:
> Some people and teams in Debian do manage their package sources in git;
> others don't. I'm not sure what the stats are at the moment for the
> various approaches; there might be a UDD script already that generates
> some. I was interested in looking at this, once upon a time.

There is indeed a regular check of VCS usage:

http://upsilon.cc/~zack/stuff/vcs-usage/

Which today lists:

arch7
bzr 199
cvs 11
darcs   832
git 12439
hg  65
mtn 23
svn 3593

Source packages using some VCS: 17169   (75.37%)

So that puts git as the declared VCS for > 50% source packages (and leading 
the next most popular by almost a factor of 4).



-- 
Stuart Prescotthttp://www.nanonanonano.net/   stu...@nanonanonano.net
Debian Developer   http://www.debian.org/ stu...@debian.org
GPG fingerprint90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7




-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/mgso52$2rc$1...@ger.gmane.org

Re: debian github organization ?

[mudongliang]

On Fri, 2015-04-17 at 17:06 +0100, Jonathan Dowland wrote: 
> On Thu, Apr 16, 2015 at 11:22:53PM +0800, mudongliang wrote:
> > But I know that debian does not manager source code by git !
> > How can it??
> 
> Some people and teams in Debian do manage their package sources in git; others
> don't. I'm not sure what the stats are at the moment for the various
> approaches; there might be a UDD script already that generates some. I was
> interested in looking at this, once upon a time.
> 
> The real question is: what do we gain by hosting such things on github?
> The social stuff, pull requests, etc.?
> 
I think hosting such things on github will encourage us to give a little
contribution to Debian!
Up to now , I don't know how to contribute to Debian,no matter what
kind!Maybe I do not focus on it!
mudongliang 


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/blu436-smtp11004ad5e0a1a2f00d065f0bc...@phx.gbl

Re: debian github organization ?

[Russ Allbery]

Ben Finney  writes:
> Russ Allbery  writes:

>> Funny, this is why I don't get why people are so upset that some use
>> GitHub. Because of how Git works, the impact of lock-in is pretty much
>> limited to the non-repository stuff (issues and so forth).

> Yet it is exactly those lock-in features that is the basis for arguments
> to put special effort into the centralised single point of failure.

> For example, the centralised proprietary GitHub “pull request” is
> presented as a reason to abandon a decentralised model:

Uh, a pull request isn't something proprietary.  It was part of the design
of Git from the beginning and is based on the workflow of the Linux
kernel.  What GitHub offers are some nice tools for managing those pull
requests that reduces the friction considerably, just like they offer a
nice web interface for viewing repositories.  Those tools are useful, and
I hope they'll be replicated in an open source framework for Git
repository management, but they're not lock-in.  You can do pull requests
without GitHub (and in fact I've done a fair bit of that).

> So upstream have chosen a proprietary lock-in service for their
> workflow. That should not put any obligation on others to also submit to
> proprietary lock-in.

Of course not.  You don't have to use anything you don't want to use, and
no one in this thread is advocating otherwise, at least that I've seen.
All that I'd ask is that, if other people want to use GitHub, for you to
not be an ass about it, the same way that we don't lecture people for
using a proprietary editor to write free sofware.  Some of us are willing
to reach out to people who are using GitHub and give and take patches from
them in their preferred way, particularly right now when there aren't a
lot of compelling alternatives to point them to.  If you aren't, that's
perfectly fine; just please don't get in the way of us who are.

There's a whole spectrum of difference within the project about how
absolute people want to personally be about only using free tools.  Some
people are at the end of the spectrum with RMS and are investigating
computers with fully free firmware, and more power to them.  Other people
are using non-free software for some things and free software for other
things and are contributing the latter to Debian.  And more power to them
as well, since they're helping us build the free software community.

Sometimes I wonder if people think free software is so fragile that if
anyone who works on it ever touches non-free software, everything we built
will crumble.  I think our community and ecosystem is a lot more robust
than that.

-- 
Russ Allbery (r...@debian.org)   


--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/874moe16n4@hope.eyrie.org

Re: debian github organization ?

[Ben Finney]

Russ Allbery  writes:

> Steve McIntyre  writes:
> > Agreed - it's really annoying to see everybody clamour for a
> > centralised single point of of failure for git hosting. :-(
>
> Funny, this is why I don't get why people are so upset that some use
> GitHub. Because of how Git works, the impact of lock-in is pretty much
> limited to the non-repository stuff (issues and so forth).

Yet it is exactly those lock-in features that is the basis for arguments
to put special effort into the centralised single point of failure.

For example, the centralised proprietary GitHub “pull request” is
presented as a reason to abandon a decentralised model:

Paul Tagliamonte  writes:

> An entirely fair point, however, I also think it's quite rude to
> ignore the workflow they've chosen for contributions -- if they expect
> PRs, it might disrupt their workflow and result in a much harder time
> for them.

So upstream have chosen a proprietary lock-in service for their
workflow. That should not put any obligation on others to also submit to
proprietary lock-in.

-- 
 \ “I went to a restaurant that serves ‘breakfast at any time’. So |
  `\I ordered French Toast during the Renaissance.” —Steven Wright |
_o__)  |
Ben Finney


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/85y4lqqkfx@benfinney.id.au

Re: MBF: build Python 3 modules for packages that support it upstream

[Paul Tagliamonte]

On Thu, Apr 16, 2015 at 06:50:11PM -0400, Paul Tagliamonte wrote:
> Severity will be wishlist. Target is the next release / sid after Jessie
> release.


Draft text and dd-list attached. Please let me know of any false
positives if you see them.

I'll start filing tomorow night.

Cheers,
  Paul

-- 
 .''`.  Paul Tagliamonte   |   Proud Debian Developer
: :'  : 4096R / 8F04 9AD8 2C92 066C 7352  D28A 7B58 5B30 807C 2A87
`. `'`  http://people.debian.org/~paultag
 `- http://people.debian.org/~paultag/conduct-statement.txt
Package: {{package}}
Severity: wishlist
User: py3porters-de...@lists.alioth.debian.org
Usertags: patchme-python3
thanks

Hello there!

This package contains a trove classifier[1] in its `setup.py` like
"Programming Language :: Python :: 3". This means that the package's upstream
developers consier this package to be ready for Python 3. This is wonderful!


As part of an ongoing process to migrate as much as we can to Python 3 to
ensure we're ready for our glorious Python 3 future, please build a Python 3
module.


If you need help doing this, please feel free to contact the Debian Python
Modules Team (DPMT), and we can help! If you would welcome a NMU, please do
let the team know (py3porters-de...@lists.alioth.debian.org).

Please upload any new versions before Jessie's release to experimental, the
Release Team has been doing such great work, it'd be a shame to see unstable
out of sync before we release!



If the reason you've not built a Python 3 module is due to the dependency
chain below you, just let me know, and I can add it to our list, or feel
free to file a bug in coordination with the team!


Have a great day, and thanks for your work!
  Paul, on behalf of the Python 3 Embetterment Squad


[1]: https://pypi.python.org/pypi?%3Aaction=list_classifiers
Adam Schmalhofer 
   execnet
   pytest-xdist

Alex Chiang 
   python-messaging

Andrea Corbellini 
   python-iowait

Andreas Tille 
   python-hl7 (U)

Angel Abad 
   glue

Ben Finney 
   python-lockfile

Bernd Zeimetz 
   flask-wtf (U)
   mod-wsgi (U)
   parsedatetime (U)
   wtforms (U)

Bjorn Ove Grotan 
   pyrad (U)

Carl Chenet 
   pycallgraph

Christophe Siraut 
   python-django-contact-form (U)

David Paleino 
   python-couchdb

David Watson 
   python-django-south

Debian Med Packaging Team 
   python-hl7

Debian Python Modules Team 
   basemap
   django-auth-ldap
   faulthandler
   flask-wtf
   mod-wsgi
   parsedatetime
   pycallgraph (U)
   pyodbc (U)
   pyquery
   pyrad (U)
   python-django-contact-form
   python-gmpy (U)
   python-http-parser
   python-meld3
   python-pgmagick
   python-pyftpdlib (U)
   python-pysnmp4-apps (U)
   python-pysnmp4-mibs (U)
   python-socketpool
   sphinx-issuetracker
   transifex-client (U)
   wtforms

Debian QA Group 
   django-authority
   python-django-treebeard

Debian Tryton Maintainers 
   relatorio

Deepak Tripathi 
   pyodbc
   python-pysnmp4-apps (U)
   python-pysnmp4-mibs (U)

Dirk Eddelbuettel 
   rpy2

Felix Geyer 
   mod-wsgi (U)

Fladischer Michael 
   sphinx-issuetracker (U)

Free Ekanayaka 
   python-pyramid-tm
   python-pyramid-zcml

Ghe Rivero 
   pysendfile

Jackson Doak 
   python-meld3 (U)

Jan Luebbe 
   python-pysnmp4-apps

Jan Lübbe 
   python-pysnmp4-mibs

Janos Guljas 
   python-pyftpdlib
   transifex-client

Jeremy Lainé 
   pyrad

John Paulett 
   python-hl7 (U)

Jonathan Wiltshire 
   pyquery (U)

Laszlo Boszormenyi (GCS) 
   python-greenlet

Laszlo Boszormenyi (GCS) 
   python-greenlet

LLVM Packaging Team 
   llvm-py

Martin Kelly 
   python-gmpy

Mathias Behrle 
   relatorio (U)

Michael Fladischer 
   django-auth-ldap (U)

Michael Hanke 
   openpyxl (U)
   pydicom (U)
   scikit-learn (U)
   statsmodels (U)

Michael Hanke 
   lazyarray (U)

Michal Čihař 
   tagpy

Miriam Ruiz 
   faulthandler (U)

NeuroDebian Team 
   openpyxl
   pydicom
   scikit-learn
   statsmodels

NeuroDebian team 
   lazyarray

Ondrej Certik 
   cython (U)

Pierre Chifflier 
   python-ptrace

Python Applications Packaging Team 
   cython

Python Modules Packaging Team 
   tagpy (U)

Sandro Tosi 
   basemap (U)

Shell Xu 
   python-snappy

Stephan Sürken 
   python-django-extensions

Sylvestre Ledru 
   llvm-py (U)

TANIGUCHI Takaki 
   pyquery (U)
   python-http-parser (U)
   python-pgmagick (U)
   python-socketpool (U)

Ulises Vitulli 
   python-pysolr

Vincent Bernat 
   snimpy

Yaroslav Halchenko 
   cython (U)
   openpyxl (U)
   pydicom (U)
   scikit-learn (U)
   statsmodels (U)

Yaroslav Halchenko 
   lazyarray (U)



signature.asc
Description: Digital signature

Re: debian github organization ?

[Russ Allbery]

Steve McIntyre  writes:
> Ben Finney wrote:
>> Paul Tagliamonte  writes:

>>> So, yes, it's nonfree. Yes, it's controlled by DDs. No, I don't think
>>> this should be the Vcs-Git: target. No, I don't think we should
>>> endorse GitHub. Yes, we need free tools. Yes, we should contribute to
>>> the F/OSS community where upstreams are.

>> That last part seems to deny the D in DVCS. Why are we under such
>> pressure to use one particular centralised service?

> Agreed - it's really annoying to see everybody clamour for a
> centralised single point of of failure for git hosting. :-(

Funny, this is why I don't get why people are so upset that some use
GitHub.  Because of how Git works, the impact of lock-in is pretty much
limited to the non-repository stuff (issues and so forth).

I use GitHub for some things, largely because it makes it easy for people
to contribute patches if they're used to that workflow, and it lets me
take advantage of some services (like continuous integration builds) that
I could but don't feel like building myself.  I also push all my
repositories to my own Git server with its own gitweb instance, so if
GitHub disappears tomorrow, I don't lose anything of much note.

Yes, it's a proprietary service and all, but not all proprietary cloud
services are created equal in terms of their lock-in and other drawbacks.
GitHub is pretty light-weight on that front.

That said, something more akin to GitHub (including the nice integration
API and fork/pull model) running on a service like Alioth would be very
neat.

-- 
Russ Allbery (r...@debian.org)   


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87iocu1fp5@hope.eyrie.org

Re: debian github organization ?

[Steve McIntyre]

Ben Finney wrote:
>Paul Tagliamonte  writes:
>
>> So, yes, it's nonfree. Yes, it's controlled by DDs. No, I don't think
>> this should be the Vcs-Git: target. No, I don't think we should
>> endorse GitHub. Yes, we need free tools. Yes, we should contribute to
>> the F/OSS community where upstreams are.
>
>That last part seems to deny the D in DVCS. Why are we under such
>pressure to use one particular centralised service?

Agreed - it's really annoying to see everybody clamour for a
centralised single point of of failure for git hosting. :-(

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"Every time you use Tcl, God kills a kitten." -- Malcolm Ray


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/e1yjfgl-0003x0...@mail.einval.com

Bug#782796: ITP: libstring-expand-perl -- string utility functions for expanding variables in self-referential sets

[Axel Beckert]

Package: wnpp
Owner: Axel Beckert 
Severity: wishlist

* Package name: libstring-expand-perl
  Version : 0.04
  Upstream Author : Paul Evans 
* URL : https://metacpan.org/release/String-Expand
* License : Artistic or GPL-1+
  Programming Lang: Perl
  Description : string utility functions for expanding variables in 
self-referential sets

String::Expand implements utility functions for expanding embedded
variables in a string. Variable references are embedded in strings in a
similar form to the Bourne shell, namely, in the form $NAME or
${NAME}. In the former case, the NAME must consist of a capital letter
or underscore, and may be followed by zero or more capital letters,
digits or underscores. In the latter case, the name can consist of any
characters, but will be terminated by the first close brace character
'}'.

This is especially useful if you want to expand environment variables
inside strings.

The string may also contain literal dollar marks, escaped by \$, and
literal escape marks, escaped by \\. These will be converted to $ and \
respectively on return.

While there are many other modules that also provide expansion such as
this, this module provides the function expand_strings(), which will
perform variable expansions in all the values in a given hash, where
values can refer to other values within the same hash.


The package is a future dependency for unburden-home-dir and will be
maintained under the umbrella of the Debian Perl Team.


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87383ymjvr@c-cactus.deuxchevaux.org

Re: debian github organization ?

[Paul Tagliamonte]

On Sat, Apr 18, 2015 at 06:03:12AM +1000, Ben Finney wrote:
> Upstream is using a decentralised VCS, it seems a little condescending
> to assume they are incapable of using it.

An entirely fair point, however, I also think it's quite rude to ignore
the workflow they've chosen for contributions -- if they expect PRs, it
might disrupt their workflow and result in a much harder time for them.

Honestly, it might mean they pull it into one of their repos and make a
PR to the canonical repo. Which is just making work for them.


Cheers,
  Paul

-- 
 .''`.  Paul Tagliamonte   |   Proud Debian Developer
: :'  : 4096R / 8F04 9AD8 2C92 066C 7352  D28A 7B58 5B30 807C 2A87
`. `'`  http://people.debian.org/~paultag
 `- http://people.debian.org/~paultag/conduct-statement.txt


signature.asc
Description: Digital signature

Re: debian github organization ?

[Ben Finney]

Paul Tagliamonte  writes:

> So, yes, it's nonfree. Yes, it's controlled by DDs. No, I don't think
> this should be the Vcs-Git: target. No, I don't think we should
> endorse GitHub. Yes, we need free tools. Yes, we should contribute to
> the F/OSS community where upstreams are.

That last part seems to deny the D in DVCS. Why are we under such
pressure to use one particular centralised service?

Upstream is using a decentralised VCS, it seems a little condescending
to assume they are incapable of using it.

-- 
 \  “Friendship is born at that moment when one person says to |
  `\another, ‘What! You too? I thought I was the only one!’” —C.S. |
_o__)Lewis |
Ben Finney


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/858udqsetb@benfinney.id.au

Re: MBF: build Python 3 modules for packages that support it upstream

[Paul Tagliamonte]

On Thu, Apr 16, 2015 at 06:50:11PM -0400, Paul Tagliamonte wrote:
> I'll curate the raw run I did today, since I saw a few false positive
> (python 3 backports to python 3) and file them. I'll run a dd-list at
> some point before the file.
> 
> Severity will be wishlist. Target is the next release / sid after Jessie
> release.

Since I've got no one complaining, I'm going to go ahead and file these
under the usertag patchme-python3, wishlist, and with a note it's for
after jessie releases. I'll compile a dd-list and run through it before
the filing.

Thanks!
  Paul

-- 
 .''`.  Paul Tagliamonte   |   Proud Debian Developer
: :'  : 4096R / 8F04 9AD8 2C92 066C 7352  D28A 7B58 5B30 807C 2A87
`. `'`  http://people.debian.org/~paultag
 `- http://people.debian.org/~paultag/conduct-statement.txt


signature.asc
Description: Digital signature

Re: debian github organization ?

[Paul Tagliamonte]

On Fri, Apr 17, 2015 at 03:36:45PM -0300, João Vanzuita wrote:
> And wanna ask you guys to answer the Jonathan Downland question bellow.
> 
> On 17/04/15 13:06, Jonathan Dowland wrote:
> >The real question is: what do we gain by hosting such things on github?
> >The social stuff, pull requests, etc.?

Uch, so I resubscribed to -devel -- it'd be nice to email the admins of
the thing you're talking about to, well, ask them.

I've been using it to create repos where I need to communicate with an
upstream on GitHub (so that it's in the Project's namespace, so it's not
locked up under github.com/paultag when I go missing), and I maintain
mirrors of repos on git.debian.org (using a VCS sync script I wrote) to
let new contributors send me patches.

Lowing the barrier to entry, and helping them work with a different
workflow (alioth, etc) once they feel comfortable contributing is much
less intimidating.


So, yes, it's nonfree. Yes, it's controlled by DDs. No, I don't think
this should be the Vcs-Git: target. No, I don't think we should endorse
GitHub. Yes, we need free tools. Yes, we should contribute to the F/OSS
community where upstreams are.


I even wrote a GitHub Pull Request -> format-patch series tool, but
never deployed it. One day when I have all the time in the world :)

Cheers,
  Paul

-- 
 .''`.  Paul Tagliamonte   |   Proud Debian Developer
: :'  : 4096R / 8F04 9AD8 2C92 066C 7352  D28A 7B58 5B30 807C 2A87
`. `'`  http://people.debian.org/~paultag
 `- http://people.debian.org/~paultag/conduct-statement.txt


signature.asc
Description: Digital signature

Re: debian github organization ?

[João Vanzuita]

That's a very nice starting point!

Maybe it's a good ideia, but I'm still asking myself why.

And wanna ask you guys to answer the Jonathan Downland question bellow.

On 17/04/15 13:06, Jonathan Dowland wrote:
The real question is: what do we gain by hosting such things on 
github? The social stuff, pull requests, etc.? 



--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/553152bd.4040...@me.com

Re: debian github organization ?

[Russ Allbery]

"Milan P. Stanic"  writes:

> What about gitolite? It is in Debian, can be used with gitweb and have
> access control.

> N.B. I'm biased (maybe) because I use gitolite for my company
> repositories.

gitolite is very nice insofar as it goes.  I've used it a lot, and still
use it in various places.  But it and GitHub are fairly different things.
It's just the repository management (with a very nice ACL system), and is
the most useful if you're following a hub and spoke model for your
repositories.  If you want the whole pull request flow, code review, or
the many nice API integrations with things like continuous build and test
of proposed merges, gitolite doesn't really help.

Another approach is Gerrit, which is very nice if you have an up-front
code review requirement, but which is hard to package given its
substantial Java dependencies.  But the world seems to be moving more
towards the GitHub pull and fork model than the Gerrit up-front code
review model.

-- 
Russ Allbery (r...@debian.org)   


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87bnim3b8l@hope.eyrie.org

Re: debian github organization ?

[Balasankar C]

On a side note to this thread, GitLab packaging for Debian is happening 
silently (and of course slowly) in the Debian Ruby group. Anyone is welcome to 
help. :)

On 17 April 2015 11:07:37 am IST, Marc Haber  
wrote:
>On Thu, 16 Apr 2015 19:40:21 -0700, Russ Allbery 
>wrote:
>>Iustin Pop  writes:
>>> I think the VCS agnosticism is actually detrimental in this context.
>>> It's much easier for the user when every repo is using the same VCS.
>>> And consistency makes it very easy, for example, to refer to commits
>>> across projects, to standardise pull/clone workflows, etc.
>>
>>+1.  VCS agnosticism means you waste a bunch of time making each new
>>feature work with every supported VCS, which can include trying to
>>shoehorn pretty foreign workflows into the model of some other VCS.
>
>But it leaves a choice to the author. On a VCS-bound system, all
>choice you have is to go to a different place.
>
>Thankfully, git is by far the best VCS on the market and the vast
>majority of people seem to agree. But imagine the outcry if ten years
>ago Sourceforge had said "our VCS is svn and we don't support anything
>else".
>
>Greetings
>Marc
>-- 
>-- !! No courtesy copies, please !!
>-
>Marc Haber |   " Questions are the | Mailadresse im
>Header
>Mannheim, Germany  | Beginning of Wisdom " |
>http://www.zugschlus.de/
>Nordisch by Nature | Lt. Worf, TNG "Rightful Heir" | Fon: *49 621
>72739834
>
>
>--
>To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
>with a subject of "unsubscribe". Trouble? Contact
>listmas...@lists.debian.org
>Archive: https://lists.debian.org/e1yiyy9-vg...@swivel.zugschlus.de

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Re: debian github organization ?

[Milan P. Stanic]

On Fri, 2015-04-17 at 16:10, Bernd Zeimetz wrote:
> On 04/16/2015 05:04 PM, Dimitri John Ledkov wrote:
> > I'd rather see gitlab.debian.net  :)
> or gitblit, which would be easier to integrate into ldap/sso/ssh imho.

What about gitolite? It is in Debian, can be used with gitweb and have
access control.

N.B. I'm biased (maybe) because I use gitolite for my company
repositories.


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150417154449.ga12...@arvanta.net

Re: debian github organization ?

[Jonathan Dowland]

On Thu, Apr 16, 2015 at 11:22:53PM +0800, mudongliang wrote:
> But I know that debian does not manager source code by git !
> How can it??

Some people and teams in Debian do manage their package sources in git; others
don't. I'm not sure what the stats are at the moment for the various
approaches; there might be a UDD script already that generates some. I was
interested in looking at this, once upon a time.

The real question is: what do we gain by hosting such things on github?
The social stuff, pull requests, etc.?


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150417160611.ga13...@chew.redmars.org

Re: debian github organization ?

[Bernd Zeimetz]

On 04/16/2015 05:04 PM, Dimitri John Ledkov wrote:
> I'd rather see gitlab.debian.net  :)

or gitblit, which would be easier to integrate into ldap/sso/ssh imho.


-- 
 Bernd ZeimetzDebian GNU/Linux Developer
 http://bzed.dehttp://www.debian.org
 GPG Fingerprint: ECA1 E3F2 8E11 2432 D485  DD95 EB36 171A 6FF9 435F


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/5531146d.7050...@bzed.de

Bug#782761: linux-tools: Please include tools/hv daemons in a binary package

[Christoph Martin]

Source: linux-tools
Version: 3.16+63
Severity: normal

the Linux kernel sources include in the tools/hv directory
tools for using Linux in MS Hyper-V virtual machines.

The tools include hv-fcopy-daemon, hv-kvp-daemon, hv-vss-daemon

Especially hv-vss-daemon is needed to be able to use
Hyper-V "Live virtual machine backup" with Windows Server 2012 R2.

https://technet.microsoft.com/en-us/library/dn614985.aspx says that
this is not supported in Debian.

It is supported in Ubuntu as they have packaged the daemons in their
linux-cloud-tools.

Red Hat supports it in the hyperv-daemons package and its dependents.

Failing to run this daemon in a VM where the backup is done via live
virtual machine backup might lead to filesystem corruption.

We had this now several times in our Hyper-V cluster. The linux kernel
gets an I/O error while trying to access the device, leading normaly
to a readonly mount of the filesystem. The filesystem has to be
manually checked.

Once we got a filesystem which was totally corrupted so that no fsck
was possible.

It would be a good idea to have this as soon as possible for jessie.

-- System Information:
Debian Release: 8.0
  APT prefers testing-updates
  APT policy: (700, 'testing-updates'), (700, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

<>

signature.asc
Description: OpenPGP digital signature

Re: debian github organization ?

[Federico Ceratto]

On Thu, Apr 16, 2015 at 6:37 PM, Sven Bartscher
 wrote:
> I don't  a reason to have gitlab/github/someother git stuff for debian,
> since we already have alioth.
> Maybe someone can enlighten me.

I'd love to see the Debian infrastructure rely of Free software,
firmware and hardware. However, we are not there yet.

GitHub is widely popular and it has become the go-to place for many
FOSS developers and *newcomers*.
Many people seem to agree that Debian is not as visible and
approachable as other projects.

Unpleasant compromises are inevitable: we are running our
infrastructure on some non-free hardware/firmware,
we host the contrib and non-free archive areas, we fetch and package
tarballs from GitHub.

I would argue that the benefits of being on GitHub in terms of
attracting new users and contributors outweighs the damage[1]

When enabling the non-free archives, users are displayed a warning.
Similarly, any Debian organization/repo on GH could be clearly marked
as a non-official/mirror.


[1] http://mako.cc/writing/hill-free_tools.html

-- 
Federico


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/cag4rqzyquvdaeoqgluufy9emft6rphwgk_zw-4_b93yt1gq...@mail.gmail.com

Re: selinux-policy-default missing in jessie

[Neil Williams]

On Fri, 17 Apr 2015 13:50:26 +0200
Tobias Bengfort  wrote:

> Hi,
> 
> I recently updated my system to jessie. I noticed that some packages
> were gone, notably selinux-policy-default. As far as I understand they
> have no chance of coming back in because jessie is already frozen. So
> do I understand correctly that SELinux will not be included in the
> upcoming version of debian? Or is there some workaround/alternative I
> do not yet know about?

policycoreutils and checkpolicy are in Jessie. It's the refpolicy
source package which was removed from Jessie in December 2014 and has 3
RC bugs.

https://tracker.debian.org/pkg/refpolicy

So it depends on your need for binaries provided by refpolicy. If I
understand it correctly, existing policies will work and policies can
still be defined but the default references have unfixed
release-criticial issues.

-- 


Neil Williams
=
http://www.linux.codehelp.co.uk/



pgpQCDRtBHWxj.pgp
Description: OpenPGP digital signature

SELinux missing in jessie

[Tobias Bengfort]

Hi,

I recently updated my system to jessie. I noticed that some packages
were gone, notably selinux-policy-default. As far as I understand they
have no chance of coming back in because jessie is already frozen. So do
I understand correctly that SELinux will not be included in the upcoming
version of debian? Or is there some workaround/alternative I do not yet
know about?


tobias


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/mgqs22$uo$1...@ger.gmane.org

Processed: Re: Bug#782749: general: All browsers except Links2 crash constantly and iceweasel is broken

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + moreinfo
Bug #782749 [general] general: All browsers except Links2 crash constantly and 
iceweasel is broken
Added tag(s) moreinfo.

-- 
782749: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782749
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/handler.s.b782749.142926640932021.transcr...@bugs.debian.org

Bug#782749: general: All browsers except Links2 crash constantly and iceweasel is broken

[Dominik George]

Control: tags -1 + moreinfo

Hi,

> All browsers I have tried but Links2 crash constantly.  Often they will not 
> run at all.

Please provide more detail about this.

Which browsers did you try: How did you install and start them? What do
they output?

> I expect the browsers to work and not crash all the time.

So do we, and I am very sure that this is what happens for most users.

> I cannot install Chromium, and cannot install iceweasel or related browsers 
> as these packages are broken.

What do you mean by saying that the „packages are broken“?

iceweasel is a bit outdated, but existent in wheezy for sparc; Chromium
is not existent for sparc, which cannot be called „broken“.

-nik



signature.asc
Description: OpenPGP digital signature

Bug#782749: general: All browsers except Links2 crash constantly and iceweasel is broken

[D. Charles Pyle]

Package: general
Severity: important

Dear Maintainer,
*** Please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these lines ***


-- System Information:
Debian Release: 7.8
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 
'stable')
Architecture: sparc (sparc64)

Kernel: Linux 3.2.0-4-sparc64
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

All browsers I have tried but Links2 crash constantly.  Often they will not run 
at all. This leaves anyone using this machine pretty upset.
I expect the browsers to work and not crash all the time.  I cannot install 
Chromium, and cannot install iceweasel or related browsers as these packages 
are broken.  Were it not for Links2 I would have no stable browsing capability 
on Debian Wheezy.


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150417100446.5329.61788.reportbug@Sparky

Concern about libdvdcss distribution (Re: (My last) bits from the DPL)

[henrich]

Hi,

> On Thu, Apr 16, 2015 at 04:47:19PM +0200, Lucas Nussbaum wrote:
> >
> > Libdvdcss and ZFS soon in Debian?
> > =
> > 
> > We received legal advice from Software Freedom Law Center about the
> > inclusion of libdvdcss and ZFS in Debian, which should unblock the
> > situation in both cases and enable us to ship them in Debian soon.

To distribute some mechanism to avoid copy protection such as DRM is 
illegal in Japanese law (Unfair Competition Prevention Act) since 2012.

It means that putting libdvdcss package into Debian repository causes 
problems in Japan, and most of organization that provides Debian mirror 
will _stop_ mirroring for Debian. Maybe libdvdcss is okay in other area, 
but not here in Japan.


So please, don't take mirrors away from Japan...

-- 
Regards,

 Hideki Yamane



-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/201504170928.t3h9spu5022...@mbox.iijmio-mail.jp

Bug#782746: ITP: rally -- benchmark System for OpenStack

[Thomas Goirand]

Package: wnpp
Severity: wishlist
Owner: Thomas Goirand 

* Package name: rally
  Version : 0.0.3
  Upstream Author : OpenStack Foundation 
* URL : https://github.com/stackforge/rally
* License : Apache-2.0
  Programming Lang: Python
  Description : benchmark System for OpenStack

 Rally is a Benchmark-as-a-Service project for OpenStack.
 .
 Rally is intended to provide the community with a benchmarking tool that is
 capable of performing specific, complicated and reproducible test cases on
 real deployment scenarios.


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/20150417091010.27640.24962.report...@buzig2.mirantis.com

Bug#782745: ITP: orocos-log4cpp -- C++ library for flexible logging

[Leopold Palomo-Avellaneda]

Package: wnpp
Severity: wishlist
Owner: "Leopold Palomo-Avellaneda" 

* Package name: orocos-log4cpp
  Version : 2.8.0
  Upstream Author : Orocos Developers 
* URL : https://github.com/orocos-toolchain/log4cpp
* License : LGPL
  Programming Lang: C++
  Description : C++ library for flexible logging

Log for C++ is a library of C++ classes for flexible logging to files,
syslog and other destinations. Orocos-log4cpp is maintained by Orocos
developers. This version of log4cpp deviates from the official release
by adding custom category factories. Orocos requires this for setting
up real-time logging.

- why is this package useful/relevant? is it a dependency for
  another package? 

Yes, orocos-ocl that belongs to orocos-toolchain (as project)

- do you use it? if there are other packages providing similar functionality, 
  how does it compare?

We use it in our lab. Yes, we have another version in debian of the same.
This is a fork, with more capabilities of log4cpp. 

I have tried to convince upstream to fusion both projects. Also I have tried
to do it myself, but I was not able to that. The orocos developers have
design their fork in the way that could be co-installabled, because they
have increased the SONAME. However, the -dev package is not co-installable
with the original one.

Also, I have renamed this version with orocos-log4cpp.
 
- how do you plan to maintain it? inside a packaging team (check list at 
https://wiki.debian.org/Teams)? 

Inside debian-science team. I have done a preliminary work in:

http://anonscm.debian.org/cgit/debian-science/packages/orocos/log4cpp.git

- are you looking for co-maintainers? do you need a sponsor?

Yes, both. Any help will be welcome. All orocos-toolkit is a complex piece
of software.


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/2015041708.10382.98554.report...@soho.upc.es

Re: debian github organization ?

[Dimitri John Ledkov]

On 16 Apr 2015 12:05 pm, "Sven Bartscher" <
sven.bartsc...@weltraumschlangen.de> wrote:
>
> On Thu, 16 Apr 2015 09:04:07 -0600
> Dimitri John Ledkov  wrote:
>
> > I'd rather see gitlab.debian.net :)
>
> I don't  a reason to have gitlab/github/someother git stuff for debian,
> since we already have alioth.
> Maybe someone can enlighten me.
>

In no particular order:
* merge proposals / code review. Mailing lists suck for this. And these
webby tools usually support email based workflow as well (to some degree)
* no approval required to create/fork projects, teams, source trees (there
are namespaces)
* syntax highlighted or rendered code browsing
* familiar user interface / concepts for most developers
* no arbitrary hooks, no direct file access to repositories, no repository
maintainance for repository owner. (These are all good things)
* restful API triggers to update things instead

We are at the tipping point were more of active developers used git and
e.g. github; than svn and source forge monsters.

My first VCS was git & repo.cz later quickly gitorious & github.

Regards,

Dimitri.

Re: debian github organization ?

[Russ Allbery]

Russell Stuart  writes:
> On Thu, 2015-04-16 at 23:13 -0700, Russ Allbery wrote:

>> However, I still stand by the decision to only support a single VCS, at
>> least when you start, because you can move a lot faster and implement a
>> lot more functionality that people care a great deal about.

> Woo, slow down there.  Here I was thinking the discussion was about
> spinning up a server using exist software.  Has the discussion moved to
> writing our own or even modifying something to suit Debian's needs?

No.  My comment was in the context of a comparison between Sourceforge and
GitHub, and I was just making the point that I think this was a wise
decision on GitHub's part.  It was also in the context of a couple of
other packages that are possible contenders for a revision control
management framework, both of which have made the same choice, also (IMO)
wisely.

> As for one DVCS to rule the world - that also sounds like a bit of a
> stretch.

While we're pondering whether dropping support for older VCSes is a bit of
a stretch, the broader software community is just shrugging and using
GitHub.  If the goal is to produce a viable free software alternative to
GitHub, supporting Subversion or bzr or Mercurial would be nowhere on my
list of requirements.

Obviously, supporting a choice of DVCSes would be great, all other things
being equal.  But given the resources available for a free software
project, all else is not going to be equal, and there are *lots* of other
features that are a much higher priority for more developers than making
the diminishing minority of people who don't use Git more comfortable.

-- 
Russ Allbery (r...@debian.org)   


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87r3rj4470@hope.eyrie.org

Re: debian github organization ?

[Marc Haber]

On Thu, 16 Apr 2015 23:13:01 -0700, Russ Allbery 
wrote:
>Marc Haber  writes:
>> Thankfully, git is by far the best VCS on the market and the vast
>> majority of people seem to agree. But imagine the outcry if ten years
>> ago Sourceforge had said "our VCS is svn and we don't support anything
>> else".
>
>Er, they did, didn't they?  I could have sworn that they only supported
>CVS initially, and then only added Subversion, and getting Git support
>took forever.

Subversion came - in my memory - rather fast after becoming available.
Only having CVS in the days when CVS was the only available VCS is
excuseable. When git came, I was already away from Sourceforge.

Greetings
Marc
-- 
-- !! No courtesy copies, please !! -
Marc Haber |   " Questions are the | Mailadresse im Header
Mannheim, Germany  | Beginning of Wisdom " | http://www.zugschlus.de/
Nordisch by Nature | Lt. Worf, TNG "Rightful Heir" | Fon: *49 621 72739834


--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/e1yj0nb-0004il...@swivel.zugschlus.de

Re: debian github organization ?

[Russell Stuart]

First a Mel Cupa.  I called the SourceForge system Apollo.  It's actual
name is Apache Allura.  Brain fart.

On Thu, 2015-04-16 at 23:13 -0700, Russ Allbery wrote:
> Er, they did, didn't they?  I could have sworn that they only supported
> CVS initially, and then only added Subversion, and getting Git support
> took forever.

Pretty much.  Of course that may have something do with the respective
VCS being born in that order.  For comparison in the speed of addition,
GutHub opened for business in April 2008.  SourceForge added support for
git in March 2009.

> However, I still stand by the decision to only support a single VCS, at
> least when you start, because you can move a lot faster and implement a
> lot more functionality that people care a great deal about.

Woo, slow down there.  Here I was thinking the discussion was about
spinning up a server using exist software.  Has the discussion moved to
writing our own or even modifying something to suit Debian's needs?  If
so, is that justified by history?  Was there a period when not only was
Alioth's bug queue serviced, but we actually did some heavy lifting?  If
not than any discussion of "adding functionality" is probably fanciful.

In any case using an existing project and contributing any changes
upstream sounds like a much better plan to me - particularly if the
project is packaged in Debian.  They means we can just install auto
upgrades to keep it secure.

As for one DVCS to rule the world - that also sounds like a bit of a
stretch.  If we are going to do that, can we also settle on a preferred
computer language and force everyone to use a single debian packaging
method?  It would make life sooo much easier.


signature.asc
Description: This is a digitally signed message part