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
* 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
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*
* 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
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 wiki
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/
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
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
* Thomas Schmitt scdbac...@gmx.net, 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
Hi Thomas
So this in libburn4.install:
debian/tmp/usr/lib/*/libburn.so.4*
You can just say usr/lib/*/libburn.so.4*
or even better
usr/lib/*/libburn.so.*
that way at the next soname bump you won't need
to change the install files too.
($somebody might object that having the 4 makes you
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
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]
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 (‘libraryname.a’) is usually provided in addition to
the shared version.”
Due to the
Hi,
i wrote:
Add myself to Uploaders ? Am i entitled ?
Christian Kastner wrote:
However: it appears that this package is team-maintained. In that case,
you leave the Maintainer as-is, and add yourself to Uploaders.
Adding myself to uploaders leads to new local warnings:
W: libburn
* Gianfranco Costamagna costamagnagianfra...@yahoo.it, 2015-08-24, 07:00:
debian/tmp/usr/include/libburn/libburn.h
debian/tmp/usr/lib/*/libburn*.a
debian/tmp/usr/lib/*/libburn.so
debian/tmp/usr/lib/*/pkgconfig/libburn-1.pc
not sure why you ship a static library,
we usually do not
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
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
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
Hi,
i worked a bit more on my local libburn package.
Shall/can i replace my yesterday upload by help of dput -f ?
Regarding http://mentors.debian.net/package/libburn ,
i have hoepfully solved the complaints under
Package closes bugs in a
Hi,
i was able to fix debuild -b with compat 9 by changing the
content of debian/libburn4.install from
debian/tmp/usr/lib/libburn.so.4* usr/lib
to
debian/tmp/usr/lib/x86_64-linux-gnu/libburn.so.4* usr/lib/x86_64-linux-gnu
Next i wanted to ask: Is this remedy a valid solution ?
But now i
On 2015-08-23 12:48, Thomas Schmitt wrote:
Hi,
Hi Thomas,
i worked a bit more on my local libburn package.
[...]
The failure of debuild -b with compat 9 still riddles me.
With 9 it finally complains
dh_install: libburn4 missing files (debian/tmp/usr/lib/libburn.so.4*),
On 2015-08-23 16:08, Thomas Schmitt wrote:
Remaining questions:
- Shall i dput -f now ?
Yes.
I don't know if you have to remove the package first (eg via the web
interface). Can someone more familiar with mentors.debian.net add some
enlightenment here?
- What to do about the complaint:
Hi,
i wrote:
$ gpg --verify ../libisoburn_1.4.0-1.1_source.changes
...
gpg: WARNING: This key is not certified with a trusted signature!
Johan Van de Wauw wrote:
This indicates that you have not set a trust level for that key. If you run
gpg --edit-key ABC0A854
type trust and set
Hi,
somehow i managed to upload the non-working
variant with
Build-Depends: dh-autoreconf, pkg-config, debhelper (= 9), libcam-dev
[kfreebsd-any]
and probably debian/compat content 9.
Can i overwrite the upload ?
If i have to make a new version, then i first wait for
some feedback.
Have a
On 20/08/15 18:33, Thomas Schmitt wrote:
- https://wiki.debian.org/DebianMentorsFaq#How_do_I_make_my_first_package.3F
Put a package together, built against a current version of sid.
I'm on Jessie 8.1. The dependencies of the packages in question
are very basic. The package sources
Hi,
thanks for the answers. They helped me to achieve progress.
So i really had to pass the can-he-install-sid-? test.
I already began installing yesterday evening.
It is instructive, but i would have preferred to postpone
the qemu adventures until i explore passthrough of DVD drives.
How
On 21/08/15 15:42, Thomas Schmitt wrote:
Well, i need to make some progress with uploading.
So i'll go on with the VM for now. I need to learn a bit more
about what sbuild does. On the long run it looks cleaner.
Hi Thomas,
sbuild basically implements what you have started to build in your VM.
Hi,
Danny Edel wrote:
Debian actually has ready-made VM scripts for you.
https://wiki.debian.org/sbuild
They urgently need advertising at the entry points
of mentors.debian.net and at the upload instructions.
call debuild -S on your host machine first:
This will create a .debian.tar.xz
Hi,
Danny Edel wrote:
The main advantage of [sbuild] is the ...and throw everything away to get a
clean starting point, so you have a reproducible and minimal build
environment.
Yep. Cleaner and thus more sensible to changes in environment.
As said, i deem the source very portable and thus
On 2015-08-21 13:21, Danny Edel wrote:
On 20/08/15 18:33, Thomas Schmitt wrote:
Else: Is there a shortcut description how to quickly set up
Debian package development in a virtual machine and how
to keep it up to date ?
(Hardware is plenty but my own VM scripts date back to Debian 6.)
On 2015-08-21 13:15, Thomas Schmitt wrote:
I already began installing yesterday evening.
It is instructive, but i would have preferred to postpone
the qemu adventures until i explore passthrough of DVD drives.
Yes, that makes sense.
How about publicly available accounts on a sid machine,
Hi,
after some fight with the keyring i am able to produce
signed packages on sid.
Will this warning be a problem ?
$ gpg --verify ../libisoburn_1.4.0-1.1_source.changes
gpg: Signature made Fri 21 Aug 2015 10:44:01 PM CEST using DSA key ID ABC0A854
gpg: Good signature from Thomas Schmitt
On Fri, Aug 21, 2015 at 11:33 PM, Thomas Schmitt scdbac...@gmx.net wrote:
Hi,
after some fight with the keyring i am able to produce
signed packages on sid.
Will this warning be a problem ?
$ gpg --verify ../libisoburn_1.4.0-1.1_source.changes
gpg: Signature made Fri 21 Aug 2015
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* what we want.
The Source package will be created by debuild -S
On 2015-08-20 18:33, Thomas Schmitt wrote:
i am the upstream developer of freshly orphaned packages libburn4,
libisofs6, libisoburn1, cdrskin, and xorriso. Now preparing to get
them in shape for sponsorship and for closing old bug reports.
By the way, in that case, you should retitle the
On 2015-08-20 18:33, Thomas Schmitt wrote:
Currently i am stuck at:
- https://wiki.debian.org/DebianMentorsFaq#How_do_I_make_my_first_package.3F
Put a package together, built against a current version of sid.
I'm on Jessie 8.1. The dependencies of the packages in question
are very
On Thu, Aug 20, 2015 at 6:33 PM, Thomas Schmitt scdbac...@gmx.net wrote:
Hi,
i am the upstream developer of freshly orphaned packages
libburn4, libisofs6, libisoburn1, cdrskin, and xorriso.
Now preparing to get them in shape for sponsorship and
for closing old bug reports.
Thanks for taking
Hi,
i am the upstream developer of freshly orphaned packages
libburn4, libisofs6, libisoburn1, cdrskin, and xorriso.
Now preparing to get them in shape for sponsorship and
for closing old bug reports.
Steve McIntyre offered his help (i hope this means
sponsorship). But knowing how busy he is, i
38 matches
Mail list logo