Fwd: Installing Debian from one hard-disk to another hard-disk.

[sooraj kenoth]

I have a completely customised Debian and ubuntu installation(Normal
installation) in my external hard-disk. I can add or remove or update
the packages from anywhere I have an internet connection.

Now I want to install the same system to another I want to by using
the installer. I can I do this?

I couldn't understand the following links:-

https://www.debian.org/releases/etch/i386/ch05s01.html.en
https://www.debian.org/releases/etch/i386/ch04s05.html.en

--
Regards
Sooraj Kenoth
"I am Being the Change I Wish to See in the World"


-- 
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/CALkky43WmxBF_yn=ozve66z9q9mw--4t5yu7jvzuqj2ew_s...@mail.gmail.com

Re: Standardizing the layout of git packaging repositories

[Manoj Srivastava]

hi,

  habit looked at both, I think I prefer got-debcherry. since it created a 
(IMHO) cleaner history, easier for me to understand and bisect.

   Manoj

On August 24, 2014 9:34:29 PM PDT, Barry Warsaw  wrote:
>On Aug 24, 2014, at 08:33 PM, Russ Allbery wrote:
>
>>git-buildpackage's gbp pq system is what I use.  I believe git-dpm is
>more
>>complicated and comprehensive, but gbp pq is simple enough in its
>>operations that it doesn't take long to wrap your mind around it.
>
>git-dpm seems pretty easy to use as well.  YMMV, but ultimately I think
>both
>helpers achieve the same goals.  Over in debian-python@ we're having
>some good
>discussions related to moving the Debian Python team over to git, and
>many
>folks have contributed useful stories and experiences.
>
>I'm beginning to think that what we want is for gbp and git-dpm to
>interoperate, such that any individual maintainer can use whichever
>tool they
>choose, but would still allow the team to adhere to consensus
>recommendations,
>so there's no guesswork involved.  E.g. the ultimate artifacts would
>end up
>being the same, regardless of whether you used gbp, git-dpm, or plain
>vanilla
>git + quilt.  One example of a superficial differences is the tag names
>used
>by default.  They're different between the two helpers, but really
>needn't be.
>
>-Barry

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

Re: Reverting to GNOME for jessie's default desktop

[Ondřej Surý]

Hey,

On Thu, Aug 21, 2014, at 17:56, Paul van der Vlis wrote:
> Hello,
> For some hardware there are no 3D drivers. E.g. in server-boards there
> are most of the time very poor GPU's. I don't use a graphical
> environment on servers myself most of the time, but I think many people
> do.

We don't have to target those (or any other weird setup) anyway with
*default* desktop environment. If anyone run graphical environment on
servers I am quite confident they can install non-default DE on the
machine.

Please, let's drop the mindset where default DE has to fit all. That's
not going to happen anyway.

O.
-- 
Ondřej Surý 
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server


--
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/1408954684.4046835.156367981.2a372...@webmail.messagingengine.com

Bug#759212: ITP: bdreader -- An e-comics reader

[Vincent]

Package: bdreader
Version: 1.02-1
Severity: wishlist

* Package name : bdreader
Version : 1.02
Upstream Author : Vincent Crocher 
* URL : http://bdreader.sourceforge.net
* License : GPL
Description : BDReader is intended to be a light and simple but comfortable
comics reader. As a main feature, BDReader includes an auto-panel detection on
comics pages. It allows you to display the panels (or squares) of a comic page
individually, in the reading order. It also offers a Preview page option,
allowing you to preview each page before reading into details the different
panels of the page.

BDReader uses the FLTK library for GUI, OpenCV for image processing, libarchive
for archive management and MuPDF for pdf files management.



-- System Information:
Debian Release: wheezy/sid
  APT prefers precise-updates
  APT policy: (500, 'precise-updates'), (500, 'precise-security'), (500,
'precise'), (100, 'precise-backports')
Architecture: amd64 (x86_64)

Kernel: Linux 3.13.0-34-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages bdreader depends on:
ii  libarchive12  3.0.3-6ubuntu1
ii  libc6 2.15-0ubuntu10.6
ii  libfontconfig12.8.0-3ubuntu9.1
ii  libfreetype6  2.4.8-1ubuntu2.1
ii  libgcc1   1:4.6.3-1ubuntu5
ii  libjbig2dec0  0.11-1ubuntu1
ii  libjpeg8  8c-2ubuntu7
ii  libopencv-core2.3 2.3.1-7
ii  libopencv-highgui2.3  2.3.1-7
ii  libopencv-imgproc2.3  2.3.1-7
ii  libstdc++64.6.3-1ubuntu5
ii  libx11-6  2:1.4.99.1-0ubuntu2.2
ii  libxext6  2:1.3.0-3ubuntu0.1
ii  libxft2   2.2.0-3ubuntu2
ii  libxinerama1  2:1.1.1-3ubuntu0.1
ii  zlib1g1:1.2.3.4.dfsg-3ubuntu4

bdreader recommends no packages.

bdreader suggests no packages.


-- 
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/20140825112430.31021.11745.reportbug@vincent-Ubuntu

daemon user naming scheme

[Jerome BENOIT]

Hello List,

is there for Debian a daemon user naming scheme or custom ?

Thanks in advance,
Jerome


-- 
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/53fb3392.9040...@rezozer.net

Re: internationalized domain name (IDN) in Debian

[Dariusz Dwornikowski]

> 
> Am Sonntag, den 24.08.2014, 20:32 +0200 schrieb Ralf Jung:
> 
> > > https://wiki.debian.org/IDN 
> 
> > > Summary: webbrowser support it in general but email clients still lack
> > > the support of it.
> > 
> > Why do you list Icedove as non-supporting? I just sent a mail to your
> > echo service, and got a reply. Is there anything else I should check?
> 
> No, this was a mistake. Just sending/recieving is my first test. This
> could be much more extended (from address with IDN, setup wizard with
> your email account with IDN domain, IDN certificates,...) but first it
> helps to know the software can send IDN emails.
> 

I have chromium on testing, IDN works but show the domain name as 
http://www.xn--kthe-5qa.de/ instead of www.köthe.de . I think this is a known 
chromium issue. 


-- 
Dariusz Dwornikowski, 
  Institute of Computing Science, Poznań University of Technology
  www.cs.put.poznan.pl/ddwornikowski/  
  room 2.7.2 BTiCW | tel. +48 61 665 29 41


signature.asc
Description: Digital signature

Bug#759244: ITP: camp -- C++ multi-purpose reflection library

[Corentin Desfarges]

Package: wnpp
Severity: wishlist
Owner: Corentin Desfarges 

* Package name: camp
  Version : 0.7.1
  Upstream Author : Laurent Gomila 
* URL : https://github.com/tegesoft/camp
* License : LGPL3, GPL3
  Programming Lang: C++
  Description : C++ multi-purpose reflection library

  CAMP is a multi-purpose reflection library developped by Technogerma Systems 
France
(http://www.tegesoft.com).

It provides an abstraction for most of the high-level concepts of C++:
- Classes
- Enumerations
- Properties
- Functions
- Objects
- Variables

By wrapping all these concepts into abstract structures, CAMP provides an extra 
layer of
flexibility to programs, and allow them to fully expose their data structures 
at runtime.

Many applications can take advantage of CAMP, in order to automate tasks which 
would
otherwise require a huge amount of work. For example, CAMP can be used to 
expose and edit
objects' attributes into a graphical user interface. It can also be used to do
automatic binding of C++ classes to script languages such as Python or Lua.
Another possible application would be the serialization of objects to XML, text 
or
binary formats. Or you can even combine all these examples to provide a powerful
and consistent interface for manipulating your objects outside C++ code.


I need to pack Camp to use it for a most important package, fw4spl 
(http://code.google.com/p/fw4spl/)


-- 
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/20140825144212.6922.92168.reportbug@debian

Re: daemon user naming scheme

[Simon McVittie]

On 25/08/14 14:01, Jerome BENOIT wrote:
> is there for Debian a daemon user naming scheme or custom ?

Several :-(

The ones I've seen suggested are (assuming a package, daemon or user
whose simple name is "foo"):

* _foo
* foo
* debian-foo
* Debian-foo
* Dfoo

 has been open
since 2004 and shows no signs of resolution.

I think I slightly prefer _foo, which originated in *BSD. However, none
of the packages I maintain actually do that; they use Debian-foo or
debian-foo for historical reasons (that seemed to be the most popular at
the time, and changing a username once you have created it is hard to
get right).

S


-- 
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/53fb4de2.9060...@debian.org

Bug#759251: ITP: ibus-sharada-braille -- Braille input engine for IBus

[Samuel Thibault]

Package: wnpp
Severity: wishlist
Owner: Samuel Thibault 

* Package name: ibus-sharada-braille
  Version : 0.1.2.99
  Upstream Author : Nalin.x.Linux 
* URL : http://ibus-sharada-braille.blogspot.in/
* License : GPLv2+
  Programming Lang: Python
  Description : Braille input engine for IBus

Ibus-sharada-braille permits to use the PC keyboard to type text in
graphical desktops in a Perkins-like way, i.e. braille patterns.

It supports several braille tables  (english, french, indian, spanish),
contracted braille and abbreviations.

It comes with table editors.


-- 
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/20140825145241.ga28...@type.bordeaux.inria.fr

Re: internationalized domain name (IDN) in Debian

[Ondřej Surý]

Hi Noël,

could you please disable Greylisting on the echo@köthe.de email?
It makes the testing more difficult than it needs to be.

Cheers,
Ondrej

On Sun, Aug 24, 2014, at 19:55, Noël Köthe wrote:
> Hello,
> 
> I'm collecting the status of IDN in Debian on
> https://wiki.debian.org/IDN 
> 
> Summary: webbrowser support it in general but email clients still lack
> the support of it.
> 
> If you could test your not listed client(s) with an IDN domain would
> help.
> 
> Thank you.
> 
> 
> -- 
> Noël Köthe 
> Debian GNU/Linux, www.debian.org
> Email had 1 attachment:
> + signature.asc
>   1k (application/pgp-signature)


-- 
Ondřej Surý 
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server


--
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/1408978503.4138720.156487781.4314e...@webmail.messagingengine.com

Re: daemon user naming scheme

[Jerome BENOIT]

Thanks for the prompt reply.

On 25/08/14 16:53, Simon McVittie wrote:
> On 25/08/14 14:01, Jerome BENOIT wrote:
>> is there for Debian a daemon user naming scheme or custom ?
> 
> Several :-(
> 
> The ones I've seen suggested are (assuming a package, daemon or user
> whose simple name is "foo"):
> 
> * _foo
> * foo
> * debian-foo
> * Debian-foo
> * Dfoo
> 
>  has been open
> since 2004 and shows no signs of resolution.
> 
> I think I slightly prefer _foo, which originated in *BSD.

Let assume this custom:
is then /var/lib/foo the custom name for its home directory ?


 However, none
> of the packages I maintain actually do that; they use Debian-foo or
> debian-foo for historical reasons (that seemed to be the most popular at
> the time, and changing a username once you have created it is hard to
> get right).
> 
> S
> 
> 
Thanks,
Jerome


-- 
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/53fb5456.2090...@rezozer.net

Bug#759255: ITP: erlang-p1-utils -- set of small Erlang libraries

[Philipp Huebner]

Package: wnpp
Severity: wishlist
Owner: Philipp Huebner 

* Package name: erlang-p1-utils
  Version : 0.2014.08.25
  Upstream Author : ProcessOne
* URL : https://github.com/processone/p1_utils
* License : GPLv2, EPL
  Programming Lang: Erlang
  Description : set of small Erlang libraries

 The libraries in this package were written for ejabberd which still
 uses them. They were split off into their own project to follow
 Erlang/OTP guidelines.

This package is required for packaging ejabberd 14.07 for Debian.


-- 
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/20140825160544.15518.81419.report...@emmagan.debalance.de

Re: internationalized domain name (IDN) in Debian

[Noël Köthe]

Hello Dariusz,

Am Montag, den 25.08.2014, 15:54 +0200 schrieb Dariusz Dwornikowski:

> > > > https://wiki.debian.org/IDN 

> I have chromium on testing, IDN works but show the domain name as 
> http://www.xn--kthe-5qa.de/ instead of www.köthe.de . I think this is a known 
> chromium issue. 

Not that I'm aware of but I can reproduce it. In Firefox moving the
mouse over the IDN links of the wiki page shows them with their non
ASCII characters and in chromium some of them are converted and shown in
punycode. I couldn't find an bugreport about it in Debian

-- 
Noël Köthe 
Debian GNU/Linux, www.debian.org


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

Re: internationalized domain name (IDN) in Debian

[Noël Köthe]

Hello Ondřej,

Am Montag, den 25.08.2014, 16:55 +0200 schrieb Ondřej Surý:

>> https://wiki.debian.org/IDN 

> could you please disable Greylisting on the echo@köthe.de email?
> It makes the testing more difficult than it needs to be.

Sorry. Yes, I need to make the echo service better but I'm not sure if
my provider gives me the possiblity to disable greylisting for only this
address. Sorry, but thanks for testing.

-- 
Noël Köthe 
Debian GNU/Linux, www.debian.org


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

Re: daemon user naming scheme

[Jerome BENOIT]

On 25/08/14 17:20, Jerome BENOIT wrote:
> Thanks for the prompt reply.
> 
> On 25/08/14 16:53, Simon McVittie wrote:
>> On 25/08/14 14:01, Jerome BENOIT wrote:
>>> is there for Debian a daemon user naming scheme or custom ?
>>
>> Several :-(
>>
>> The ones I've seen suggested are (assuming a package, daemon or user
>> whose simple name is "foo"):
>>
>> * _foo
>> * foo
>> * debian-foo
>> * Debian-foo
>> * Dfoo
>>
>>  has been open
>> since 2004 and shows no signs of resolution.
>>
>> I think I slightly prefer _foo, which originated in *BSD.

Moreover, _foo is not accepted by adduser, the option --force-badname must be 
used.

> 
> Let assume this custom:
> is then /var/lib/foo the custom name for its home directory ?
> 
I have just realized that I should avoid this question.



>  However, none
>> of the packages I maintain actually do that; they use Debian-foo or
>> debian-foo for historical reasons (that seemed to be the most popular at
>> the time, and changing a username once you have created it is hard to
>> get right).
>>
>> S
>>
>>
> Thanks,
> Jerome
> 
> 


-- 
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/53fb72d0.2050...@rezozer.net

Re: internationalized domain name (IDN) in Debian

[Milan P. Stanic]

On Mon, 2014-08-25 at 15:54, Dariusz Dwornikowski wrote:
> > Am Sonntag, den 24.08.2014, 20:32 +0200 schrieb Ralf Jung:
> > > > https://wiki.debian.org/IDN 
> > > > Summary: webbrowser support it in general but email clients still lack
> > > > the support of it.
> > > 
> > > Why do you list Icedove as non-supporting? I just sent a mail to your
> > > echo service, and got a reply. Is there anything else I should check?
> > No, this was a mistake. Just sending/recieving is my first test. This
> > could be much more extended (from address with IDN, setup wizard with
> > your email account with IDN domain, IDN certificates,...) but first it
> > helps to know the software can send IDN emails.
> I have chromium on testing, IDN works but show the domain name as 
> http://www.xn--kthe-5qa.de/ instead of www.köthe.de . I think this is a known 
> chromium issue. 

In my chromium it show it as http://www.köthe.de
chromium  35.0.1916.153-1~deb7u1 amd64

-- 
Kind regards,  Milan


--
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/20140825175316.ga9...@arvanta.net

Re: daemon user naming scheme

[Simon McVittie]

On 25/08/14 18:30, Jerome BENOIT wrote:
>> On 25/08/14 16:53, Simon McVittie wrote:
>>> I think I slightly prefer _foo, which originated in *BSD.
> 
> Moreover, _foo is not accepted by adduser, the option --force-badname must be 
> used.

Correct. Debian-foo has the same property; debian-foo does not.

Depending who you ask, that might be a disadvantage (you're using a
'bad' character in a username) or an advantage (you're using a character
that is unlikely to be used by sysadmins for an actual human's account,
because they would have to specify --force-badname in order to do so).

>> Let assume this custom:
>> is then /var/lib/foo the custom name for its home directory ?
>>
> I have just realized that I should avoid this question.

It is reasonable to use /var/lib/foo (or /run/foo or /var/cache/foo or
/var/games/foo) as the home directory of a system user whose name is
_foo, debian-foo, Debian-foo or whatever.

It would also be reasonable to use the package name, or any other
obviously-related unique string, as the basename of their home
directory. (openarena-server creates the user Debian-openarena whose
home is /var/games/openarena-server.)

If they don't need a home directory at all, it would also be reasonable
to use /nonexistent, as long as you make sure not to create it.

S


-- 
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/53fb8872.7050...@debian.org

Re: Bug#759014: RFP: bitcointrader -- Bitcoin trading application

[Daniel Pocock]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256




On 23/08/14 21:42, Dmitry Smirnov wrote:
> Package: wnpp Severity: wishlist X-Debbugs-CC:
> debian-devel@lists.debian.org,pkg-bitcoin-de...@lists.alioth.debian.org
>
>  Package name: bitcointrader Version: 1.07.99 Upstream Author: July
> IGHOR  URL:
> https://github.com/JulyIGHOR/QtBitcoinTrader License: GPL-3+ with
> OpenSSL linking exception Description: Bitcoin trading application 
> QtBitcoinTrader is a front-end to cryptocurrency exchanges. It
> helps to open and cancel orders very fast and monitor data in real
> time. .

Could this link against the OpenMAMA packages to get real-time
currency rates?

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Icedove - http://www.enigmail.net/

iQIcBAEBCAAGBQJT+4j0AAoJEGxlgOd711bEcRYQAJrhgbXi4vY6BK0HDvReooC1
GXlPaNnRvLWeblyGqVKxsFX9Bnhq+YQM7ad3cPt07E0GCJe4TucETz8DpH1h0HaX
13+ustbPZ0zc2jIRQyU4pTCvj8n9hQgZhzTSo7Srd5VNkSrnh1reOCuzFYGbr4/c
R6VdxMFvJJV43UFN7JQKAFdl+M+VY+G87m7I+YX+E7GM4xgxGP3cpeENKniLs5Ae
nfHzy4EocA0ZGKd64uW/raV3e15XoxIWhW8FkElGmFBo9u4Y/VrwgRasfmjEXOiI
KrWZa09IscqeUJkEg3ZMP8ktqUgYdGliZiBINTFuWOrSPt6CrPFO2L3xiFyqSQ2j
AhKBtsjA7A/mAU9o58fSCDeXDAGWX7bmVUPugtw+uNbbFtkRBNAlGrfsiYLwm/0g
uRSQFY2UpGw/5XC9+4Jsv9+K+PCYlQj4A0QzRwZ+H4Ljavn7Xv6XnFJhC2pgFo64
B+kKHBB5uxpV513g67zDk0Jz+JPu3ipHqWnowVQs6kJWlohYdU/z1RrCFoFRPmHL
wCK0glAjxV/Ls17H+sGJGhrW8aN6gF99YaNQNv5hWMLSKj/RG3leDWUYfaeGcmzk
6poHlafO+Ac8jsfI4IjekxcSBIESxFcQ94hOAfVFM3Cu9LxIdKxemBzXWeRmFiAB
Te+ArxaxEG2zf2LDn99Y
=wfBh
-END PGP SIGNATURE-


-- 
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/53fb88f5.2050...@pocock.pro

Re: bits from the DPL -- mid-April to mid-August 2014

[Steve Langasek]

On Sun, Aug 24, 2014 at 09:28:11AM -0700, Lucas Nussbaum wrote:
> Debian logo now registered as a trademark
> =

> Thanks to the work of the Debian trademark team and the Software Freedom
> Law Center (SFLC), the Debian logo is now officially registered as a
> trademark, as can be seen on [1].

> [1] http://tdr.uspto.gov/search.action?sn=86037470

This is a much welcome surprise.  Kudos to everyone involved in making this
happen at last. :)

> Assets - meetings, sprints, conferences
> ===

> DebConf'15 kick-off meeting
> ---
> The DebConf'15 team organized a kick-off meeting on May 3rd in Heidelberg
> (in the to-be DC15 venue). It gathered 17 members of the team.  See [1]
> for details.
> Cost for Debian: 1700€

> [1] https://wiki.debconf.org/wiki/DebConf15/Germany/KickoffMeeting

Does this come out of the DebConf15 budget?

> Tails Hackfest
> --

> Cost for Debian: 5000€

> systemd + GNOME sprint
> --

> Cost for Debian: 2000€

> bootstrap sprint
> 

> Cost for Debian: 3000€

> DebianMed sprint
> 

> Amount allocated: 1600€ (if 4 DD attend) or 2000€ (if 5 DD)

> Travel sponsorship for GSOC students at DebConf'14
> --
> In order to enable our GSOC students to attend DebConf'14, I
> authorized the use of $6138. This comes in addition to Google's
> sponsoring of the travel for $500 per student.

> MiniDebConf India
> -
> A MiniDebConf is being organized in India on October 17-18.
> Details: https://wiki.debian.org/DebianIndia/MiniDebConf2014/Kollam
> I authorized the use of 4500€, to help fund the travel of Debian
> contributors and speakers to the event.

Does this list of expenses mean that you now have a good overview of
Debian's cash flow?  In April, I understood that this was a major
outstanding problem.  I'm happy to see that we are spending Debian money on
useful sprints and events; I would be happier to have oversight of the
overall Debian balance sheet.

Thanks,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: Digital signature

Bug#759294: ITP: gcc-arm-none-eabi -- GCC cross compiler for ARM Cortex-A/R/M processors

[Agustin Henze]

Package: wnpp
Severity: wishlist
Owner: Agustin Henze 
X-Debbugs-CC: debian-devel@lists.debian.org, debian-cr...@lists.debian.org

   Package name: lm4tools
Version: 20140816+a565880
Upstream Author: 2011-2012 Texas Instruments Incorporated
URL: https://launchpad.net/gcc-arm-embedded
License: BSD (3 clause), GPL-2+
Description: Command-line firmware flashing tool to communicate with the
Stellaris Launchpad and remote GDB socket over USB for Stellaris Launchpad ICDI
 .
 The Stellaris Launchpad is a low cost development board created by Texas
 Instruments that comes with an ARM Cortex-M4F processor


-- 
TiN



signature.asc
Description: OpenPGP digital signature

Re: bits from the DPL -- mid-April to mid-August 2014

[Paul Wise]

On Mon, Aug 25, 2014 at 2:13 PM, Steve Langasek wrote:

> Does this list of expenses mean that you now have a good overview of
> Debian's cash flow?  In April, I understood that this was a major
> outstanding problem.  I'm happy to see that we are spending Debian money on
> useful sprints and events; I would be happier to have oversight of the
> overall Debian balance sheet.

One of the Debian auditors was at the ledger BoF, we briefly discussed
Debian's accounting situation. The biggest problem appears to be lack
of ability to get detailed data out of the various TOs.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


-- 
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/caktje6f7jpze06jtib8oond6hcqpzsfdsfyflxtlmke3mev...@mail.gmail.com

Re: incoming.debian.org opens its doors to the public

[Al]

unsubscribe


On Sat, Aug 16, 2014 at 3:07 PM, Ansgar Burchardt  wrote:

> Hi,
>
> incoming.debian.org is used to publish recently uploaded source and
> binary packages before they reach the mirror network of the main
> archive. Until now, however, with the exception of the buildd network,
> it has not been possible to verify the integrity of the files. This was
> traditionally because we did not want to load ftp-master.debian.org by
> many users downloading files.
>
> Several people informed us that it would make their work on Debian
> easier, if they had a way to securely access these packages. So we
> decided to implement some changes to incoming.debian.org:
>
> First, the archive used by buildds is now publically accessible in
> http://incoming.debian.org/debian-buildd/. This location provides access
> to all recently uploaded packages, split into individual suites, and
> provides the neccessary metadata for APT to verify the integrity of the
> published files. See [1] for details.
>
>   [1] 
>
> Secondly, source and binary packages are no longer published directly on
> http://incoming.debian.org/. Instead, people are encouraged to use the
> pool layout described above which is configured per-suite and contains
> Release files which have been signed in the normal way.
>
> We would also like to thank the Debian System Administration team who
> quickly setup the static mirror setup for the new incoming.d.o, thus
> making this possible.  We would also like to thank the wanna-build and
> buildd team for making the relevant changes to the buildds quickly so
> that we could make this change live.
>
> Ansgar
>

Re: bits from the DPL -- mid-April to mid-August 2014

[Lucas Nussbaum]

On 25/08/14 at 14:13 -0700, Steve Langasek wrote:
> On Sun, Aug 24, 2014 at 09:28:11AM -0700, Lucas Nussbaum wrote:
> > Debian logo now registered as a trademark
> > =
> 
> > Thanks to the work of the Debian trademark team and the Software Freedom
> > Law Center (SFLC), the Debian logo is now officially registered as a
> > trademark, as can be seen on [1].
> 
> > [1] http://tdr.uspto.gov/search.action?sn=86037470
> 
> This is a much welcome surprise.  Kudos to everyone involved in making this
> happen at last. :)
> 
> > Assets - meetings, sprints, conferences
> > ===
> 
> > DebConf'15 kick-off meeting
> > ---
> > The DebConf'15 team organized a kick-off meeting on May 3rd in Heidelberg
> > (in the to-be DC15 venue). It gathered 17 members of the team.  See [1]
> > for details.
> > Cost for Debian: 1700€
> 
> > [1] https://wiki.debconf.org/wiki/DebConf15/Germany/KickoffMeeting
> 
> Does this come out of the DebConf15 budget?

No. AFAIK there isn't any DebConf15 budget yet, or at least it hasn't
been discussed with me yet.  (not implying that this is a bad thing at
this point, of course).

(I will reply to your other point in another mail)
 
Lucas


signature.asc
Description: Digital signature

Re: bits from the DPL -- mid-April to mid-August 2014

[Lucas Nussbaum]

Hi,

On 25/08/14 at 14:46 -0700, Paul Wise wrote:
> On Mon, Aug 25, 2014 at 2:13 PM, Steve Langasek wrote:
> 
> > Does this list of expenses mean that you now have a good overview of
> > Debian's cash flow?  In April, I understood that this was a major
> > outstanding problem.  I'm happy to see that we are spending Debian money on
> > useful sprints and events; I would be happier to have oversight of the
> > overall Debian balance sheet.
> 
> One of the Debian auditors was at the ledger BoF, we briefly discussed
> Debian's accounting situation. The biggest problem appears to be lack
> of ability to get detailed data out of the various TOs.

I've been working on that recently, and I'll present results during
Thursday's "bits from the DPL" talk. I don't have a good understanding
of Debian's detailed financial flows due to the lack of detailed data,
esp from SPI, as pointed by Paul. But at least I am now fully confident
that the 10,000 feet view looks fine, and that we can afford spending a
bit more if useful & needed. Details on Thursday.
 
Lucas


-- 
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/20140825234848.gb1...@xanadu.blop.info

Re: Standardizing the layout of git packaging repositories

[Brian May]

Ok, so I have looked at both gbp-pq and git-dpm.

To me, the key difference is different way they store the patches. There
are minor differences in user interfaces, etc, however I don't consider
these to be so important.

(apologies if this has already been said or contradicted, I am finding it
hard to keep up with these threads)


gbp-pq
-
Tutorial: https://honk.sigxcpu.org/piki/development/debian_packages_in_git/

In gbp-pq, the authoritative source is always the patches in
debian/patches. The patch-queue is just for convenience, so you can update
patches with standard git commands. There is no history kept of the
patch-queue branch. Possibly the patch-queue branch shouldn't be pushed to
remote repositories, because rebasing is expected. This makes it simple.
History is kept of debian/patches. It is not possible to refer to patches
with commit id, because this won't last a rebase or reedit. However,
comparing different Debian versions with patches applied won't be so easy,
you will have to check out two copies, manually apply the patches, and then
do a diff.

git-dpm
--
Tutorial: http://git-dpm.alioth.debian.org/examples.html

git-dpm keeps every version of every patch in git. As a result, every patch
in debian/patches has a hash referencing the git commit. After merged into
the Debian branch, this hash will not disappear even if the patch is
deleted or changed. You can provide the commit id of the patch, if ever
required (most cases the latest patch file might be better choice). As
above, history is also kept of the debian/patches directory. I believe if
you do a diff between two debian tags you will get the patches included.

summary
---
There are two options I haven't looked at: dgit and git-debcherry (or is
that got-debcherry?) - mainly because I can't find these using Google.

gbp-pq and git-dpm are not compatible methods. It is not possible to
use git-dpm or a gbp-pq repostory or vis versa. If you use gbp-pq on
a git-dpm repository, it will work, however, you will not preserve the
patches in git where git-dpm expects to find them. So git-dpm will get
confused and do the wrong thing the next time it is run.

Somebody mentioned the ease of bisect. If you bisect a gbp-pq tree, you
won't get the patches applied unless your testing does this. If you bisect
the git-dpm tree, you will get the patches applied. bisecting on the Debian
branch should be easy enough I think, despite the extra merges. I haven't
done this myself.

I am tending to side towards the git-dpm, because I like the idea of every
git commit being preserved.

gbp-pq feels to me like a version of quilt enhanced to support git for
making local changes. As such if you want to work locally on a project
without git-dpm support, and you don't want to change that, gbp-pq might be
the best choice. Which is a lot better then basic quilt, however not as
good as git-dpm for distributed development.

I hope I haven't made too many mistakes :-)
-- 
Brian May 

Re: Standardizing the layout of git packaging repositories

[Manoj Srivastava]

hi.

   http://people.debian.org/~srivasta/Serializing_Git_Branches.pdf has a 
demonstration of the differences in history given an upstream and two feature 
branches with two commits each, using git-dpm and git-debcherry.

   Manoj

On August 25, 2014 11:01:17 PM PDT, Brian May  
wrote:
>Ok, so I have looked at both gbp-pq and git-dpm.
>
>To me, the key difference is different way they store the patches.
>There
>are minor differences in user interfaces, etc, however I don't consider
>these to be so important.
>
>(apologies if this has already been said or contradicted, I am finding
>it
>hard to keep up with these threads)
>
>
>gbp-pq
>-
>Tutorial:
>https://honk.sigxcpu.org/piki/development/debian_packages_in_git/
>
>In gbp-pq, the authoritative source is always the patches in
>debian/patches. The patch-queue is just for convenience, so you can
>update
>patches with standard git commands. There is no history kept of the
>patch-queue branch. Possibly the patch-queue branch shouldn't be pushed
>to
>remote repositories, because rebasing is expected. This makes it
>simple.
>History is kept of debian/patches. It is not possible to refer to
>patches
>with commit id, because this won't last a rebase or reedit. However,
>comparing different Debian versions with patches applied won't be so
>easy,
>you will have to check out two copies, manually apply the patches, and
>then
>do a diff.
>
>git-dpm
>--
>Tutorial: http://git-dpm.alioth.debian.org/examples.html
>
>git-dpm keeps every version of every patch in git. As a result, every
>patch
>in debian/patches has a hash referencing the git commit. After merged
>into
>the Debian branch, this hash will not disappear even if the patch is
>deleted or changed. You can provide the commit id of the patch, if ever
>required (most cases the latest patch file might be better choice). As
>above, history is also kept of the debian/patches directory. I believe
>if
>you do a diff between two debian tags you will get the patches
>included.
>
>summary
>---
>There are two options I haven't looked at: dgit and git-debcherry (or
>is
>that got-debcherry?) - mainly because I can't find these using Google.
>
>gbp-pq and git-dpm are not compatible methods. It is not possible to
>use git-dpm or a gbp-pq repostory or vis versa. If you use gbp-pq on
>a git-dpm repository, it will work, however, you will not preserve the
>patches in git where git-dpm expects to find them. So git-dpm will get
>confused and do the wrong thing the next time it is run.
>
>Somebody mentioned the ease of bisect. If you bisect a gbp-pq tree, you
>won't get the patches applied unless your testing does this. If you
>bisect
>the git-dpm tree, you will get the patches applied. bisecting on the
>Debian
>branch should be easy enough I think, despite the extra merges. I
>haven't
>done this myself.
>
>I am tending to side towards the git-dpm, because I like the idea of
>every
>git commit being preserved.
>
>gbp-pq feels to me like a version of quilt enhanced to support git for
>making local changes. As such if you want to work locally on a project
>without git-dpm support, and you don't want to change that, gbp-pq
>might be
>the best choice. Which is a lot better then basic quilt, however not as
>good as git-dpm for distributed development.
>
>I hope I haven't made too many mistakes :-)
>-- 
>Brian May 

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

Re: internationalized domain name (IDN) in Debian

[Dariusz Dwornikowski]

On 25.08.14 19:53:53, Milan P. Stanic wrote:
> On Mon, 2014-08-25 at 15:54, Dariusz Dwornikowski wrote:
> > > Am Sonntag, den 24.08.2014, 20:32 +0200 schrieb Ralf Jung:
> > > > > https://wiki.debian.org/IDN 
> > > > > Summary: webbrowser support it in general but email clients still lack
> > > > > the support of it.
> > > > 
> > > > Why do you list Icedove as non-supporting? I just sent a mail to your
> > > > echo service, and got a reply. Is there anything else I should check?
> > > No, this was a mistake. Just sending/recieving is my first test. This
> > > could be much more extended (from address with IDN, setup wizard with
> > > your email account with IDN domain, IDN certificates,...) but first it
> > > helps to know the software can send IDN emails.
> > I have chromium on testing, IDN works but show the domain name as 
> > http://www.xn--kthe-5qa.de/ instead of www.köthe.de . I think this is a 
> > known chromium issue. 
> 
> In my chromium it show it as http://www.köthe.de
> chromium  35.0.1916.153-1~deb7u1 amd64
> 
> -- 

This is funny. In my chromium http://www.köthe.de get rewritten to
http://www.xn--kthe-5qa.de/, whereas polish IDN domains stay the way
they should http://żaba.pl/ or http://żółć.pl . 

chromium 35.0.1916.153-2 amd64


-- 
Dariusz Dwornikowski, 
  Institute of Computing Science, Poznań University of Technology
  www.cs.put.poznan.pl/ddwornikowski/  
  room 2.7.2 BTiCW | tel. +48 61 665 29 41


signature.asc
Description: Digital signature