On 2023-11-21 16:39 +, David James wrote:
> Dear Mentors,
>
> I would like to package the Citra emulator in the future. There are currently
> a few dependencies that need to be added as packages before Citra itself can
> be built from a tarball.
>
> A couple of these dependencies have no ve
On Tue, Nov 21, 2023 at 04:39:42PM +, David James wrote:
> A couple of these dependencies have no version upstream. Is there a
> precedent for this? Can these dependencies be packaged?
There are definitely packages like that in Debian and the usual practice
is using date-based versions, probabl
Dear Mentors,
I would like to package the Citra emulator in the future. There are currently a
few dependencies that need to be added as packages before Citra itself can be
built from a tarball.
A couple of these dependencies have no version upstream. Is there a precedent
for this? Can these de
On Wed, Jun 14, 2023 at 11:27 AM David Given wrote:
>
> The sad thing is that bazel, which is the least bad build system I've ever
> used, works in a way that's completely antithetical to how Debian wants to
> build things: it doesn't want to use host software for anything and will,
> e.g., dow
On Wed, 14 Jun 2023 at 09:35, Paul Wise wrote:
[...]
> The upstream repo seems to use bazel as its build system, at least
> according to the README. Is that not usable here? The bazel tool
> appears to be packaged in bazel-bootstrap in Debian.
>
bazel-bootstrap is very old, unfortunately --- it'
On Tue, 2023-06-13 at 19:22 +0200, Oliver Reiche wrote:
> 1. Due to the missing build description, is it ok if the maintainer
> provides a Makefile for building the C++ libraries in ./debian?
...
> 4. Such a Makefile (and control file) will be quite lengthy.
The upstream repo seems to use bazel a
Dear mentors,
Wookey and I are trying to come up with a sane concept to package the
googleapis project [1]. During our initial investigation a few
questions came up that we would like to discuss publicly.
BACKGROUND:
'googleapis' is a collection of protocol buffer [2] files, an
On Mon, May 29, 2023 at 6:24 PM Tadeu Sampaio wrote:
>
> Thx Robin for the fast response! So what is needed in order to proceed with
> the ITP below, we need a sponsor?
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024547
>
> Best regards,
> Tadeu
The (currently) last message [1] on tha
On Mon, May 29, 2023 at 01:24:12PM -0300, Tadeu Sampaio wrote:
> Thx Robin for the fast response! So what is needed in order to proceed with
> the ITP below, we need a sponsor?
Unless it's your ITP you should contact the current ITP owner so that you
don't make duplicate work.
Thx Robin for the fast response! So what is needed in order to proceed with
the ITP below, we need a sponsor?
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024547
Best regards,
Tadeu
On Mon, May 29, 2023 at 12:53 PM Robin Gustafsson wrote:
> Hi,
>
> On Mon, May 29, 2023 at 5:36 PM Tadeu S
Hi,
On Mon, May 29, 2023 at 5:36 PM Tadeu Sampaio wrote:
>
> Hi, thx for your attention! Please, can you clarify this for me? For an ITP
> to be submitted, it is necessary that the person applies to become a member
> (Debian New Maintainers)? I am asking regarding this ITP:
> https://bugs.debi
Hi, thx for your attention! Please, can you clarify this for me? For an ITP
to be submitted, it is necessary that the person applies to become a member
(Debian New Maintainers)? I am asking regarding this ITP:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024547
Thx,
Tadeu
On Thu, Oct 13, 2022 at 03:16:01PM +, Debora Velarde wrote:
> Hi everyone,
>
> I have been trying to create an update to an existing package. It currently
> doesn't use an epoch number and I need to add one. A couple questions:
If the package is for a Debian upload, befo
require to introduce an epoch?
A couple questions:
1. Is there a good package that uses an epoch number that I could
look to for an example?
The package "python-django" comes to my mind, which is now at epoch 3,
and also has some explanation in its changelog at
https://metadata.f
Hi everyone,
I have been trying to create an update to an existing package. It currently
doesn't use an epoch number and I need to add one. A couple questions:
1. Is there a good package that uses an epoch number that I could look to
for an example?
2. When I create the ta
On Sun, 2022-09-11 at 21:40 +0200, Philippe SWARTVAGHER wrote:
> Upstream has several files describing copyrights of the project [1-4].
> In d/copyright, I licensed the whole project with Apache 2.0, with
> "Google Inc." as copyright holder. Should I detail more?
Generally, the ftp-masters requir
Hello,
I created the shaderc package (see
https://salsa.debian.org/phsw/shaderc) and its almost ready for upload
(and RFS!). Yet, I have few questions:
* Copyright
Upstream has several files describing copyrights of the project [1-4].
In d/copyright, I licensed the whole project with Apache
On Thu, May 26, 2022 at 11:31:22PM +0200, Philippe SWARTVAGHER wrote:
> - dpkg-shlibdeps: warning: can't extract name and version from library
> name 'libdia.so'
I think you can ignore these.
> - W: dia source: debian-rules-sets-DEB_BUILD_OPTIONS (line 10)
>
> Parallel builds may cause a build er
Hello,
I'm trying to adopt and update the dia package, as my first contribution
to Debian packaging.
I managed to update the package to the current upstream version (not the
easiest thing: the project moved from autotools to meson since the last
package update) and fix some lintian issues.
I th
On 22/09/2020 16:05, Mattia Rizzolo wrote:
> Hi Alec,
>
> On Tue, Sep 22, 2020 at 10:48:39AM +0200, Alec Leamas wrote:
>>> I have problems with the debugging info containing the local build path
>>> and the buildinfo. Status:
[snip]
> You misread the dpkg-genbuildinfo(1) manpage, the correct env
Hi Alec,
On Tue, Sep 22, 2020 at 10:48:39AM +0200, Alec Leamas wrote:
> > I have problems with the debugging info containing the local build path
> > and the buildinfo. Status:
> >
> > As uploaded, the Build-Path stanza is not part of buildinfo. As I
> > understand it, this is inconsistent with t
On 22/09/2020 10:29, Tobias Frost wrote:
> Hi mentors,
> - Forwarded message from Alec Leamas -
>
> Date: Sun, 20 Sep 2020 20:56:57 +0200
> From: Alec Leamas
> To: Tobias Frost
> Subject: cxx-serial
> User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101
> Thunderbird/68
Hi mentors,
Forwarded with permissionis from Alec.
I don't know the correct answer atm, need to do research on that.
Maybe someon here can help ;-)
Cheers,
tobi
- Forwarded message from Alec Leamas -
Date: Sun, 20 Sep 2020 20:56:57 +0200
From: Alec Leamas
To: Tobias Frost
Subject: cx
Hello everyone I do have some changes I want to make to the package to make it
more comfortable to use.
Before the first use the looking-glass host (this package) requires some
changes to the libvirt-qemu abstract apparmor profile. Explicility changing
"/{dev,run}/shm r," to read-write
The prob
On Mon, Jan 7, 2019 at 11:06 PM Lennart Weller wrote:
> The last change is something maybe for the future. The software depends on a
> client component for windows which currently needs to be downloaded from the
> authors website. I imagine one could supply a self cross-compiled windows
> execu
Hello everyone I do have some changes I want to make to the package to make it
more comfortable to use.
Before the first use the looking-glass host (this package) requires some
changes to the libvirt-qemu abstract apparmor profile. Explicility changing
"/{dev,run}/shm r," to read-write
The prob
On Tue, Nov 13, 2018 at 4:51 PM Birger Schacht wrote:
> i let ratt rebuild all the reverse dependencies, but i'm not sure about
> the results [0]. there are some build failures that don't seem to have
> anything to do with libjson, i.e. [1] which seems to fail because of a
> directory permission p
hi,
thanks for the detailed explanation and the link to the wiki page- that
was exactly what i was looking for!
On 11/08/2018 03:05 AM, Paul Wise wrote:
> The package ratt (Rebuild All The Things) can be used to rebuild
reverse deps.
i let ratt rebuild all the reverse dependencies, but i'm not s
Since this is an orphaned package, any uploads would be referred to as
"QA upload" (dch --qa) rather than NMUs.
Looking at #904418, it seems that the test rebuild of all reverse
dependencies was not fully completed so there could be more than just
OpenSIPS affected.
The package ratt (Rebuild All
Hello mentors,
I would like to get the sway window manager into unstable. Sway has a
build dependency on libjson-c-dev (>=0.13). I'm trying to wrap my head
around the possibilities to help out with this, but i'm not sure if i
understand the dependencies correct, so i welcome any pointers to
explan
Jongmin Kim writes:
> In case of git repository, it is possible to extract all the author's
> information by tracking the commit history.
Bear in mind that copyright law leaves plenty of ways that there is no
connection betwee “person who authored the work” versus “entity who
holds copyright in
A lot of appreciating all for your kind suggestions!
On Wed, Aug 29, 2018 at 09:15:32AM +1000, Ben Finney wrote:
> The “Machine-readable debian/copyright file” specification allows
> free-form text in the “Copyright” field.
>
> With that said, in my opinion you should strongly prefer the canonic
On Wed, 29 Aug 2018 08:23:29 -0400, Tong Sun wrote:
> > You can also check the file with: cme edit dpkg-copyright.
> >
> > These tools require cme packages with its recommended dependencies.
>
> cme - Check or edit configuration data with Config::Model
>
> This is not the cme packages that you w
On Wed, Aug 29, 2018 at 4:41 AM Dominique Dumont wrote:
>
>
> Note that the copyright file can be generated from sources:
..
> You can also check the file with: cme edit dpkg-copyright.
>
> These tools require cme packages with its recommended dependencies.
cme - Check or edit configuration data
On Tuesday, 28 August 2018 00:23:08 CEST Jongmin Kim wrote:
> I'm new to packaging, and I am currently trying to write 'd/copyright'
> file. I am watching some other repositories for studying the
> conventions.
Note that the copyright file can be generated from sources:
https://wiki.debian.org/C
t doesn't belong in the
“Copyright” field.
There is already an appropriate field, “Source”, where the URL for the
upstream source can be declared.
> Now I have some questions:
> - Is it a one of the conventions? Can I write like that?
The “Machine-readable debian/copyright file” sp
ub.com/authorname'.
Even though the upstream source has their explicit copyright
information--like 'year name'-- in copyright file--like 'LICENSE.txt'.
Now I have some questions:
- Is it a one of the conventions? Can I write like that?
- Why use only the author&
Hello debian-mentors,
i'm in the process of packaging 'bolt', the thunderbolt 3 device
manager. I've pushed the current state of the package to salsa [0].
There are still some lintian warnings about missing copyright
informations, but those are about manpage files, dockerfiles,
systemd-servic
On Fri, 21 Apr 2017 10:58:30 +0100
Ghislain Vaillant wrote:
> If the corresponding Vcs-* fields in d/control are missing for these
> packages, then the packaging work is not stored in a VCS. You may
> generate one by calling `gbp import-dscs $PACKAGE` which will download
> all previous uploads an
On Fri, Apr 21, 2017 at 05:37:19PM +0900, JungHwan Kang wrote:
> 4. Some packages don't have repository(No repository found by debcheckout
> tool)
>
> like acpi, alsamixergui, apg, aspell-en, autoconf.
>
> Are there repositories for source code of those packages ?
>
% dgit clone ac
Hi,
>> 3. In case of darcs package, debcheckout tried to download source code from
>> Darcs repository.
>> (anonscm.debian.org/cgi-bin/darcsweb.cgi)
>> But, that failed. Because, the project doesn’t exist in the repository. Is
>> this working well?
>
>If it failed, probably the answer is
On Fri, 2017-04-21 at 17:37 +0900, JungHwan Kang wrote:
> Hi,
> I was analyzing repositories of debian packages by debcheckout tool.
> I've known there are 7 types of version control system.
> (Arch, Bazzar, CVS, Darcs, Git, Mercurial, Subversion)
> My questions are below...
Hi,
I was analyzing repositories of debian packages by debcheckout tool.
I've known there are 7 types of version control system.
(Arch, Bazzar, CVS, Darcs, Git, Mercurial, Subversion)
My questions are below...
1 All version control systems are using actively? or moving t
P.S. git://repo.or.cz/muse-el.git is another possible valid source,
and also has gpg-signed releases/tags. I'm unclear whether the github
repo is the master or the mirror.
signature.asc
Description: Digital signature
On Tue, Aug 30, 2016 at 09:26:24AM +, Gianfranco Costamagna wrote:
> Hi,
>
>
>
> >> Also, it's now xz compressed, which I anticipated is something
> >> Gianfranco might hassle me about if I didn't enable haha.>
> >
> >If you're not uploading a new upstream version you can't change the
> >tar
Hi,
>> Also, it's now xz compressed, which I anticipated is something
>> Gianfranco might hassle me about if I didn't enable haha.>
>
>If you're not uploading a new upstream version you can't change the
>tarball compression (unless you're changing the source package name,
>which I don't recommen
Hello,
On Mon, Aug 29, 2016 at 07:05:59PM -0400, Nicholas D Steeves wrote:
> Also, it's now xz compressed, which I anticipated is something
> Gianfranco might hassle me about if I didn't enable haha.
If you're not uploading a new upstream version you can't change the
tarball compression (unless y
On 29 August 2016 at 17:15, James Cowgill wrote:
> On 29/08/16 21:49, Nicholas D Steeves wrote:
>> Hi,
>>
>> I'm adopting muse-el. Right now it's a work-in-progress. The steps I
>> took to fixup this package can be found here:
>>
>> https://github.com/sten0/muse-el
>> clone: https://github.com/s
Hi Sean,
On 29 August 2016 at 17:35, Sean Whitton wrote:
> Hello,
>
> On Mon, Aug 29, 2016 at 10:15:08PM +0100, James Cowgill wrote:
>> > Finally, is now the time to fix the
>> > debian-rules-missing-recommended-target warning? I'm saving homepage
>> > and Vcs fields for last.
>>
>> Yes, those t
Hello,
On Mon, Aug 29, 2016 at 10:15:08PM +0100, James Cowgill wrote:
> > Finally, is now the time to fix the
> > debian-rules-missing-recommended-target warning? I'm saving homepage
> > and Vcs fields for last.
>
> Yes, those targets are required by policy (even though there are masses
> of pac
On 29/08/16 21:49, Nicholas D Steeves wrote:
> Hi,
>
> I'm adopting muse-el. Right now it's a work-in-progress. The steps I
> took to fixup this package can be found here:
>
> https://github.com/sten0/muse-el
> clone: https://github.com/sten0/muse-el.git
>
> I've also uploaded a package, with
On 29 August 2016 at 16:49, Nicholas D Steeves wrote:
> Hi,
>
> I'm adopting muse-el. Right now it's a work-in-progress. The steps I
> took to fixup this package can be found here:
>
> https://github.com/sten0/muse-el
> clone: https://github.com/sten0/muse-el.git
>
> I've also uploaded a package
Hi,
I'm adopting muse-el. Right now it's a work-in-progress. The steps I
took to fixup this package can be found here:
https://github.com/sten0/muse-el
clone: https://github.com/sten0/muse-el.git
I've also uploaded a package, with "-sa" full sources for review here:
https://mentors.debian.net/
* Paul Wise , 2016-07-30, 15:16:
I myself use Alioth, Savannah, SourceForge, GitHub and LaunchPad for
different projects. There are no hosting facilities that I personally
like, mostly because they are all web services.
There are many command-line tools that let you distance yourself from
the
On Tue, Jul 26, 2016 at 8:57 PM, Albert van der Horst wrote:
> Do you really demand that a Debian package can generate windows
> executables, and booting floppies in double density?
We already have tested and working GCC cross-compilers for Windows.
https://packages.debian.org/search?keywords=mi
Paul Wise schreef op 2016-07-26 07:15:
On Tue, Jul 26, 2016 at 3:01 AM, Albert van der Horst wrote:
It has been published, the generic system is GPL as well.
It is on the net since ages
http://home.hccnet.nl/a.w.m.van.der.horst/ciforth-5.0.tar.gz and
http://home.hccnet.nl/a.w.m.van.der.horst/ci
On Tue, Jul 26, 2016 at 3:01 AM, Albert van der Horst wrote:
> It has been published, the generic system is GPL as well.
> It is on the net since ages
> http://home.hccnet.nl/a.w.m.van.der.horst/ciforth-5.0.tar.gz and
> http://home.hccnet.nl/a.w.m.van.der.horst/cifgen.html
>
> I doubt that any one
On 07/25/2016 09:28 PM, Albert van der Horst wrote:
> Christian Seiler schreef op 2016-07-25 18:14:
>> I don't quite get what you mean, I never had any problem with
>> that.
>
> {Probably going off topic here]
> A pure assembler file means full control over section names, their
> properties (in pa
Christian Seiler schreef op 2016-07-25 18:14:
On 07/25/2016 02:51 PM, Albert van der Horst wrote:
The problem is: ld is not stable w.r.t. linking pure assembler files.
How so?
$ cat write.s
.text
.global _start
.type _start, @function
_start:
mov $1, %rax
mov %rax,
Albert van der Horst schreef op 2016-07-25 18:00:
Oorspronkelijke bericht
Onderwerp: Re: Preliminary questions for sponsoring a compiler
Datum: 2016-07-25 16:15
Afzender: Paul Wise
Ontvanger: Albert van der Horst
Not sure why you moved the discussion off-list, in Debian we
On 07/25/2016 02:51 PM, Albert van der Horst wrote:
> The problem is: ld is not stable w.r.t. linking pure assembler files.
How so?
$ cat write.s
.text
.global _start
.type _start, @function
_start:
mov $1, %rax
mov %rax, %rdi
lea str, %rsi
mov
Oorspronkelijke bericht
Onderwerp: Re: Preliminary questions for sponsoring a compiler
Datum: 2016-07-25 16:15
Afzender: Paul Wise
Ontvanger: Albert van der Horst
Not sure why you moved the discussion off-list, in Debian we prefer to
discuss things in public. Feel free to
I didn't mean to put this off list, my bad.
Oorspronkelijke bericht
Onderwerp: Re: Preliminary questions for sponsoring a compiler
Datum: 2016-07-25 15:58
Afzender: Albert van der Horst
Ontvanger: Paul Wise
Paul Wise schreef op 2016-07-25 15:12:
On Mon, Jul 25, 2016 at
On Mon, Jul 25, 2016 at 8:51 PM, Albert van der Horst wrote:
> Question 1: Am I obliged to supply a .s file and linking prescripts?
You need to supply the upstream source code and build system. If those
are the upstream source code and build system, then yes.
> (Because fasm is not in main)
fas
Dear mentors,
Since 2002 lina is a stable Forth compiler under x86 linux (And
compatible compilers available for OSX, win32 ).
From the beginning it has been fully documented using texinfo, plus a
man-page, that documents the options and a judicious excerpt.
lina page
http://home.hccnet.nl/a
On 23/07/16 01:07, Ferenc Wágner wrote:
>> - Can I push the backport branches to the repositories in [1]?
>
> Yes, please do so. Please discuss the necessary changes on our mailing
> list beforehand, I'd like to keep the delta small.
>
>> - What should the changelog entry look like? "Backport to
Etienne Dysli-Metref writes:
> I would like to backport Shibboleth packages [1] to jessie and wheezy.
>
> - What branch name should I use?
> Documentation for git-buildpackage [2] says "debian/" so that
> would yield "debian/jessie-backports-sloppy", but I've seen
> "backports/" earlier so I'm un
On 22/07/16 14:15, Alexander Wirt wrote:
>> And the distribution field should be the backport target
>> (jessie-backports-sloppy), right?
> Depends on your backport. The one that matches to your backport. And
> jessie-backports-sloppy is in every case wrong at this point in time.
Ah right, yes! t
On Fri, 22 Jul 2016, Etienne Dysli-Metref wrote:
> Thank you Alex :)
>
> On 22/07/16 13:16, Alexander Wirt wrote:
> >> - Can I push the backport branches to the repositories in [1]?
> > The backports team doesn't care about the git, you will have to ask the
> > other
> > maintainers.
>
> Ok
>
Thank you Alex :)
On 22/07/16 13:16, Alexander Wirt wrote:
>> - Can I push the backport branches to the repositories in [1]?
> The backports team doesn't care about the git, you will have to ask the other
> maintainers.
Ok
>> - What should the changelog entry look like? "Backport to "?
> That +
On Fri, 22 Jul 2016, Etienne Dysli-Metref wrote:
> Hello mentors,
>
> I would like to backport Shibboleth packages [1] to jessie and wheezy.
>
> - What branch name should I use?
> Documentation for git-buildpackage [2] says "debian/" so that
> would yield "debian/jessie-backports-sloppy", but I'
Hello mentors,
I would like to backport Shibboleth packages [1] to jessie and wheezy.
- What branch name should I use?
Documentation for git-buildpackage [2] says "debian/" so that
would yield "debian/jessie-backports-sloppy", but I've seen
"backports/" earlier so I'm unsure.
- Can I push the ba
Hi,
>> you already are a DM, you need the guest account, but it isn't requested
>> for collab-maint access
>
>You mean guest account of porterbox, right?
>I already applied, and got approved. It's for debug FTBFS of libcork
>on s390x/ppc64/sparc64.
>
>For access collab-maint, guest account of ali
Dear G,
Thanks for your quick response!
On Wed, Jun 29, 2016 at 9:43 PM, Gianfranco Costamagna
wrote:
> Hi,
>
>>Now I already have acess to collab-maint (though I didn't do any work
>
>>yet), and I have become DM [0].
>
> you already are a DM, you need the guest account, but it isn't requested
>
Hi,
>Now I already have acess to collab-maint (though I didn't do any work
>yet), and I have become DM [0].
you already are a DM, you need the guest account, but it isn't requested
for collab-maint access
>Could you kindly help to set up a git repo for shadowsocks-libev on
collab-maint?
./
Dear G,
Greetings after 1+ months for this thread!
On Thu, May 19, 2016 at 12:32 AM, Gianfranco Costamagna
wrote:
>
>
> Hi, alternative proposal
>
>>Now I understand my todo-list, briefly:
>>- package libraries first: libcork/ipset
>>- create debian/watch and ds repack
>>- RFS shadowsocks-libev
the other two.
> - show your git skills in the meanwhile, and ask for collab-maint access
>
> (BTW it isn't requested to have the repo in collab-maint by the current
> policy)
Dear G,
I followed most of your advice, and just uploaded to mentors.
I didn't package ipset becaus
Hi, alternative proposal
>Now I understand my todo-list, briefly:
>- package libraries first: libcork/ipset
>- create debian/watch and ds repack
>- RFS shadowsocks-libev
>- apply for collab-maint access
- open ITP bugs for all the libraries (search for wnpp and ITP on google)
- package libcor
On Thu, May 19, 2016 at 12:04 AM, Gianfranco Costamagna
wrote:
>
> Hi,
>
>
>>If so, here's our alioth account: rosh-guest, hosiet-guest,
>>madeye-guest.>Thank you!
>
>
> you need to send a request to join collab-maint, an alioth account doesn't
> grant
> your permissions automatically.
> I sugge
Hi,
>If so, here's our alioth account: rosh-guest, hosiet-guest,
>madeye-guest.>Thank you!
you need to send a request to join collab-maint, an alioth account doesn't grant
your permissions automatically.
I suggest you to use an external repository to show your skills, and then ask
to join
(c
[Add Max and Boyuan from upstream to CC]
Thanks Gianfranco and Jakub!
I comment when I still have question, for other parts I'll follow your
suggestion.
On Wed, May 18, 2016 at 7:13 PM, Jakub Wilk wrote:
> * Roger Shimizu , 2016-05-18, 02:14:
>>
>> Some questions/issu
* Roger Shimizu , 2016-05-18, 02:14:
I'm doing ITP packaging on shadowsocks-libev. I have a few questions in
detail.
I have set up a git repo on github: https://github.com/rogers0/shadowsocks-libev
My current changes are pushed to branch: RFC
Package builds fine with command: gbp buildpa
Hi,
>I have set up a git repo on github:
>https://github.com/rogers0/shadowsocks-libev
>My current changes are pushed to branch: RFC
(I won't clone that right now, only answering questions)
>Package builds fine with command: gbp buildpackage -us -uc --git-ignore-branch
yo
Dear mentors list,
I'm doing ITP packaging on shadowsocks-libev. I have a few questions in detail.
I have set up a git repo on github: https://github.com/rogers0/shadowsocks-libev
My current changes are pushed to branch: RFC
Package builds fine with command: gbp buildpackage -us -uc
* Johannes Schauer , 2015-08-31, 17:06:
So please don't further advertise the -d or --dist option anymore if
you actually want to use the -c or --chroot option instead!
Um, except that -d/--dist is obligatory. Without it you get:
No distribution defined
indeed I must've made an error when te
Hi,
Quoting Jakub Wilk (2015-08-31 16:02:38)
> * Johannes Schauer , 2015-08-31, 15:53:
> >>From now on, "sbuild --dist sid --arch amd64 path/to/my.dsc" works.
> >
> >It must be mentioned that a common problem with sbuild is, that the
> >.changes file it generates will have a *different* distribut
* Johannes Schauer , 2015-08-31, 15:53:
From now on, "sbuild --dist sid --arch amd64 path/to/my.dsc" works.
It must be mentioned that a common problem with sbuild is, that the
.changes file it generates will have a *different* distribution from
the one you set in debian/changelog if you use t
Hi,
Quoting Danny Edel (2015-08-21 13:43:41)
> On 21/08/15 13:21, Danny Edel wrote:
> > Once sbuild is setup
>
> Just to clarify. In this use case (using sbuild as close to buildd as
> possible), the steps labeled "for personal use" in
> https://wiki.debian.org/sbuild#Configuration
> are *not* wh
On Sat, Aug 29, 2015 at 10:11 AM, Paul Wise wrote:
> db.debian.org is planned to be rewritten with python/django.
... and help is needed for that.
https://github.com/LucaFilipozzi/ud/
--
bye,
pabs
https://wiki.debian.org/PaulWise
http://bonedaddy.net/pabs3/
http://wiki.openmoko.org/wiki/User:
On Fri, Aug 28, 2015 at 8:41 PM, Jakub Wilk wrote:
> db.debian.org should be probably fixed show SHA256 fingerprints (in addition
> to MD5 fingerprints).
db.debian.org is planned to be rewritten with python/django.
> You can use the "www.debian.org" pseudo-pacakge for the wiki, I guess...
The w
* Thomas Schmitt , 2015-08-28, 17:06:
After learning that it is a feature of Sid's ssh client, it was not too
hard to find
ssh -o FingerprintHash=md5 svn.debian.org
which displays
RSA key fingerprint is MD5:d7:0b:26:5c:7a:5d:56:40:a9:e0:5d:f4:e1:70:88:bf.
Jessie's ssh client says by defau
Hi,
sorry for the noise.
After learning that it is a feature of Sid's ssh client,
it was not too hard to find
ssh -o FingerprintHash=md5 svn.debian.org
which displays
RSA key fingerprint is MD5:d7:0b:26:5c:7a:5d:56:40:a9:e0:5d:f4:e1:70:88:bf.
Jessie's ssh client says by default:
RSA ke
Hi,
i am trying to follow the instructions for SSH setup with
alioth, after having been accepted as project member of
https://alioth.debian.org/projects/pkg-libburnia/
and promoted to admin in one sweep.
The project has an SVN and two mailing lists.
A ssh-rsa key has been uploaded via
https:/
Hi,
gregor herrmann wrote:
> You're uploading to ftp.upload.debian.org and not to mentors.d.n.
Duh (once again). This explains a lot.
Meanwhile i bothered it with a libisofs upload attempt, too.
Need to make me an upload script.
I began to write quite a desparate answer to Gianfranco
and to thin
On Mon, 24 Aug 2015 12:50:04 +0200, Thomas Schmitt wrote:
> I configured dput for http, as shown in
> http://mentors.debian.net/intro-maintainers
>
> Strangely it said "ftp" and not "http" in its messages:
>
> -
> $ dput -f li
Hi Thomas,
If you dput $something, you need to wait until $something is processed,
any later upload will fail because you can't overwrite the files
in ftp unprocessed queue.
So wait for the upload, get the email confirmation, and then dput again.
According to the log you posted, seems that dpu
Hi,
Gianfranco Costamagna:
> (please open an RFS if you need a sponsor, otherwise it might be difficult
> to track packages reviews and to actually have an upload)
I will do if my direct approach to already interested
people yields no success.
But currently i seem to have upload problems.
> [1
Hi Thomas,
(please open an RFS if you need a sponsor, otherwise it might be difficult
to track packages reviews and to actually have an upload)
>There will be no SONAME change as long as i am the upstream
>developer. ABI compatibility is one of the most important
>goals of my development.
this
low me to apply
for sponsorship by others: #796145, #796146, #796147.
I thought they were orphaned since two years, when George
told me he could not longer maintain them. But that
last step was made only a few days ago, when he was
pointed by a bystander to my questions on debian-user.
We do not spl
On Mon, Aug 24, 2015 at 11:25 AM, Jakub Wilk wrote:
> Um, no. We have literally thousands of packages shipping static libraries
> (in addition to shared libraries). Policy §8.3 says:
> “The static library (‘’) is usually provided in addition to
> the shared version.”
Due to the downsides we shoul
1 - 100 of 922 matches
Mail list logo
