On Sat, 20 Jul 2013 19:58:52 +0300, Anton Gladky wrote:
> [Quoting your private mail to me, hoping there is nothing private]
No problem, it shouldn't have been private in the first place :)
Cheers,
gregor
--
.''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
: :'
Hi Oliver,
[Quoting your private mail to me, hoping there is nothing private]
2013/7/19 Oliver Sander :
>> You want to upload
>> a newer version without intend to maintain it. Right?
>>
> No. I made up my mind and I promise to be the dcraw maintainer if that
> is what it takes.
The package cann
Hi Oliver,
i do not really have any motivation to discuss
"social" questions any more. You want to upload
a newer version without intend to maintain it. Right?
2013/7/18 Oliver Sander :
> Hi Anton,
>
>
>>> Problem is, I don't understand how much these rules apply to me, since
>>> the actual uploa
Hi Anton,
Problem is, I don't understand how much these rules apply to me, since
the actual upload to unstable will not be done by me. That case is
not covered by the text.
It does not matter, who "physically" uploads the package e.g. sponsors it.
In this case you are the author of changes.
2013/7/12 Oliver Sander :
> I kind of knew these rules, but it's good to now the details anyway.
>
> Problem is, I don't understand how much these rules apply to me, since
> the actual upload to unstable will not be done by me. That case is
> not covered by the text.
It does not matter, who "phys
Am 11.07.2013 22:45, schrieb Anton Gladky:
2013/7/11 Oliver Sander:
I don't understand. I am not the maintainer, hence what I am doing
is a NMU, hence the NMU number? Please tell me the version number
you want and I'll use it.
Hmm, please, read, when you are allowed to do NMUs.
http://www.d
2013/7/11 Oliver Sander :
> I don't understand. I am not the maintainer, hence what I am doing
> is a NMU, hence the NMU number? Please tell me the version number
> you want and I'll use it.
Hmm, please, read, when you are allowed to do NMUs.
http://www.debian.org/doc/manuals/developers-referen
Add to description something like: "Fixing lintiant warnings in manpages".
I will do that, but please comment on my questions below first.
Plus, we are now at dcraw-9.19-1.1, because upstream has made two new
releases
in the meantime.
,,,1.1 is not correct version number. You are not doing
Hi,
2013/7/9 Oliver Sander :
> I am getting one new lintian warning:
>
> I: dcraw source: quilt-patch-missing-description
> remove_LO_line_from_manpage.diff
>
> I split that patch off from the remaining ones, because it was obviously a
> separate thing. But not knowing manpage syntax at all I hav
Thanks for the hints, I just uploaded a new version.
That's a thing that I still don't understand. In an AutoTools environment
all you need is configure.in and Makefile.in. The files configure and
Makefile are then created automatically. However when I remove configure
and Makefile from the p
Hi Oliver,
in attachment is the my suggestion of debian-directory of this package.
2013/6/25 Oliver Sander :
>> Yes, but in the previous uploaded version there are in "patch-section"
>> only Makefile, badpixels and manpages. You have now also configure,
>> Makefile.in etc.
>
>
> That's a thing t
Hi Anton,
I finally got around to looking at the package again.
Currently getsource doesn't run due to some minor upstream format change.
Can you fix that?
I fixed the first bug it runs into. It still doesn't seem to work, though.
No idea what is missing.
Yes, but in the previous uploade
Hi Oliver,
2013/6/3 Oliver Sander :
> [...]
> Currently getsource doesn't run due to some minor upstream format change.
Can you fix that?
> It is what you get when following the official Debian instructions
> for switching from source format 1.0 to 3.0 (quilt).
Yes, but in the previous uploaded
Hi Anton,
I finally found the time to look at the dcraw package again.
lintian reports three problems with this package, which I don't
know how to fix:
P: dcraw: no-upstream-changelog
There really is no upstream changelog. What to do?
Id upstream does not ship it, you can do nothing with th
Hi Oliver,
> lintian reports three problems with this package, which I don't
> know how to fix:
>
> P: dcraw: no-upstream-changelog
> There really is no upstream changelog. What to do?
Id upstream does not ship it, you can do nothing with that.
> W: dcraw source: package-needs-versioned-debh
Hi Anton,
thanks for the quick reply. You are right: I should have asked the
maintainers before. My apologies. I needed the package for myself,
and then figured why not learn how to upload?
I'm not surprised that the packaging is old. I basically just took the
last package und stuffed in the n
Hi Oliver,
thanks for providing the new version of the package!
But to do such uploads you should be or (co)maintainer of the package or
at least to get a permission from the current maintainer (CC-ing him),
as the package has not been orphaned.
From the technical point of view the package needs
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "dcraw"
* Package name: dcraw
Version : 9.17-1
Upstream Author : Dave Coffin, dcoffin a cybercom period net
* URL : http://www.cybercom.net/~dcoffin/dcraw/
* Licens
18 matches
Mail list logo
